Skip to content

CI: Update sync pipeline runner#104

Open
Finii wants to merge 1 commit into
mainfrom
bugfix/sync-pipeline
Open

CI: Update sync pipeline runner#104
Finii wants to merge 1 commit into
mainfrom
bugfix/sync-pipeline

Conversation

@Finii

@Finii Finii commented Jun 22, 2026

Copy link
Copy Markdown
Member

[why]
The sync pipeline fails always.
There is no ubuntu20 runner anymore.

[how]
Be more generic, we just use git commands and do not care for OS details at all.

[why]
The sync pipeline fails always.
There is no ubuntu20 runner anymore.

[how]
Be more generic, we just use git commands and do not care for OS details
at all.

Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
@Finii Finii added the ci Continuous integration label Jun 22, 2026
@Finii

Finii commented Jun 22, 2026

Copy link
Copy Markdown
Member Author

Further questions (possibly to @alt-graph)

  • Do we want to archive GUL14 (here and on Gitlab)
  • The same sync pipeline exists in GUL17/20, but I can not find their Gitlab repo? Maybe remove.
  • Maybe stop syncing for GUL14 (and possibly remove mirror from Gitlab, or at least archive?)

@alt-graph

Copy link
Copy Markdown
Member
* Do we want to archive GUL14 (here and on Gitlab)

I wouldn't do that yet for the Github repo. It is still in use in several older projects. I don't care about the Gitlab mirror – if you agree, we can archive it and stop syncing.

* The same sync pipeline exists in GUL17/20, but I can not find their Gitlab repo? Maybe remove.

Agreed.

* Maybe stop syncing for GUL14 (and possibly remove mirror from Gitlab, or at least archive?)

Yes, makes sense. Should we still merge this PR then?

@alt-graph alt-graph left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@Finii

Finii commented Jun 23, 2026

Copy link
Copy Markdown
Member Author

I could not archive on Gitlab, but I stopped the CI and made the code invisible there.
I'll ask Tim if he can do that (i.e. archive it).

I wouldn't do that yet for the Github repo. It is still in use in several older projects.

But that is not hindered by archiving. That just closes Issues and PRs and makes the project read-only.

image

Should we still merge this PR then?

Probably not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci Continuous integration

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants