New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(gitlab-ci): ref add logic for updating non top level include
s
#16819
feat(gitlab-ci): ref add logic for updating non top level include
s
#16819
Conversation
include
sinclude
s
This is awesome. We really need this Gitlab CI ref support before we can use renovate in our enterprise |
This would be awesome to be able to support Gitlab refs at all levels. |
lib/modules/manager/gitlabci-include/__snapshots__/extract.spec.ts.snap
Outdated
Show resolved
Hide resolved
@astellingwerf @fredrondina any updates on when this will land? |
lib/modules/manager/gitlabci-include/__snapshots__/extract.spec.ts.snap
Outdated
Show resolved
Hide resolved
@viceice, @astellingwerf, @secustor, @fredrondina Looks like this is coming along nicely. Do you think this will land this week? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we should probably merge both managers before this PR as planned for future
lib/modules/manager/gitlabci-include/__fixtures__/gitlab-ci.5.yaml
Outdated
Show resolved
Hide resolved
Hey @viceice. Would it be possible to get this in first? My company is transitioning to Gitlab CI and wants to adopt renovate and move away from dependabot since dependabot does not support gitlab includes. We are using a lot of gitlab triggers that include refs. Renovate does not currently bump those refs since they are not top level. This is stopping us from launching renovate. |
you need at least fix all requested changes |
Requested changes have been made, ready for re-review |
Any updates on this? |
@viceice, @secustor , @astellingwerf , @rarkins , @fredrondina is this close? If not then we will need to launch Renovate with gitlab ci support turned off. |
I am still having issues with the CLA check, I think it is due to some of my commits not being verified. What is the best step for me to take to get this last check passing? |
probably squash or rebase your commits and fix author. |
f9c798c
to
bc2180c
Compare
squashed and rebased in order to fix commit verification |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is your chance to sneak something extra in, because I'm just gonna assume that the squashed commit is identical to the 25+ earlier commits combined.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nothing changed from gut perspective 👍
include
sinclude
s
Any idea when this will be merged? |
That won't be until at least after the conflicts are resolved. |
Ok, can I rebase to fix the conflict, and then force push back to my branch? |
no, please do merge commit with the fix |
Pull request was converted to draft
d37bd79
Merge conflicts resolved, ready for re-review |
🎉 This PR is included in version 32.161.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Changes
Context
Current gitlab-ci ref bump logic only accounts for
include
sections that are at the top level of the .gitlab-ci.yml. This does not allows for the pipeline ref's contained within any subsection (such as within another job) of the .yml file to be updated. This pattern is commonly seen in .gitlab-cy.yml files used to configure parent child pipelines.Closes #16833
Closes #9610
Documentation (please check one with an [x])
How I've tested my work (please tick one)
I have verified these changes via: