Skip to content
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

Merge gitlabci-include to gitlabci manager #21446

Open
Tracked by #25608 ...
viceice opened this issue Apr 12, 2023 · 6 comments
Open
Tracked by #25608 ...

Merge gitlabci-include to gitlabci manager #21446

viceice opened this issue Apr 12, 2023 · 6 comments
Labels
breaking Breaking change, requires major version bump manager:gitlabci GitLab CI config files priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others type:feature Feature (new functionality)
Milestone

Comments

@viceice
Copy link
Member

viceice commented Apr 12, 2023

What would you like Renovate to be able to do?

The gitlabci-include manager should be merged into gitlabci manager. Both work on same files beside the include manager also follows Gitlab inclcudes and processes them if they are local.

If you have any ideas on how this should be implemented, please tell us here.

  • merge the manager code
  • migrate gitlabci-include config to gitlabci config

Is this a feature you are interested in implementing yourself?

Maybe

@viceice viceice added type:feature Feature (new functionality) priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others breaking Breaking change, requires major version bump manager:gitlabci GitLab CI config files status:ready labels Apr 12, 2023
@viceice
Copy link
Member Author

viceice commented Apr 12, 2023

Maybe we can do it in without breaking

@rarkins
Copy link
Collaborator

rarkins commented Apr 12, 2023

Any changes to depType needed to differentiate them afterward?

@viceice
Copy link
Member Author

viceice commented Apr 12, 2023

gitlabci-includes only uses repository

function extractDepFromIncludeFile(
includeObj: GitlabIncludeProject
): PackageDependency {
const dep: PackageDependency = {
datasource: GitlabTagsDatasource.id,
depName: includeObj.project,
depType: 'repository',
};
if (!includeObj.ref) {
dep.skipReason = 'unknown-version';
return dep;
}
dep.currentValue = includeObj.ref;
return dep;
}

gitlabci also traverses local includes, so we do that twice for docker images in gitlabci and for repository includes at gitlabci-includes 🙈

@viceice
Copy link
Member Author

viceice commented Apr 12, 2023

ProgammingLanguage=docker will be applied then 😕

export const language: ProgrammingLanguage = 'docker';

@viceice viceice mentioned this issue Aug 17, 2023
5 tasks
@viceice viceice mentioned this issue Mar 18, 2024
23 tasks
@TimKnight-DWP
Copy link
Contributor

@viceice ->
gitlabci-includes handles the following types:

include:
  - project: my-proj/pipelines/node-pipeline
    file: pipeline/node-pipeline.yml
    ref: 2.5.0

whereas gitlabci handles docker tags etc referenced in a gitlab-ci.yml e.g.

    image: renovate/renovate:37-slim@sha256:4bfa4c3ec7c3ddf695283a6b22c3019ac77503597e5ad836ab3b34288a8cc961

I've seen you comment on: #14177 about issues when pinning digests in gitlabci-includes manager.

Would this change ensure that includes don't try and pin, as there is no SHA to pin, but that image references could still be pinned automatically?

@viceice
Copy link
Member Author

viceice commented Jun 11, 2024

yes

@HonkingGoose HonkingGoose mentioned this issue Jun 26, 2024
7 tasks
@viceice viceice added this to the v39 milestone Jul 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking Breaking change, requires major version bump manager:gitlabci GitLab CI config files priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others type:feature Feature (new functionality)
Projects
None yet
Development

No branches or pull requests

4 participants
@viceice @rarkins @TimKnight-DWP and others