New rules syntax and detached pipelines

Hi,

thanks for bringing this to our attention. I’d like to share some updates and clarifications, including hopefully useful details too

There was a misunderstanding about the term “deprecation”, sorry about that.

only/except are not deprecated

We have discussed this in the last couple of days, and have made it more clear that only/except are not deprecated. The new rules keywords allows to build more fine granular conditions and you are encouraged to use them.

CI/CD Template changes in 13.0

The real change now happens under the hood: GitLab provides several built-in templates, you may have seen that for CI config for Golang or Docker. There are also portions for the Auto-DevOps and Security CI/CD pipelines.

These config templates will be moved over the rules set in 13.0, with literally no visible change.

Important Change

rules and only/except cannot co-exist. CI/CD YAML syntax reference | GitLab

The transition for the Security templates is explained here: Application security | GitLab

Adjusted information

• Clarify only/except => rules notice in 13.0 breaking changes blog
• Add more specific title to help with clarity on 12.10 blog post for only/except
• Remove pre-deprecation notice for only/except
• Update rules breaking change in 13.0: rules and only/except cannot co-exist

More Rules References

• workflow:rules docs
• Disable runs for tags
• Only run for Merge Requests

Design Insights

Lessons learned

• Deprecation and Removal are strong words which may be understood and used in the wrong context.
• Use better issue titles and avoid actions like pre deprecation or subject to deprecation anywhere else.
• Provide migration guides and examples to allow changes by example.

https://twitter.com/j4yav/status/1258351162782363648

Cheers,
Michael