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

tree: drop support for cosaDir #125

Draft
wants to merge 4 commits into
base: main
Choose a base branch
from
Draft

Conversation

jlebon
Copy link
Member

@jlebon jlebon commented Oct 17, 2022

Support for the cosa directory being different from the working
directory makes implementation details messier.

Drop support for it.

Callers can still have their cosa directories be different from the
Jenkins workspace by first wrapping calls to the cosa APIs here in a
call to dir(cosaDir):

dir(cosaDir) {
        cosaBuild(skipKola: true)
        kola()
        kolaTestIso(skipMetal4k: true)
}

The cosa directory currently needs to be a subdirectory of the workspace
(see #124).

We've moved away from Gangplank for now in favour of `podman remote`:
coreos/coreos-assembler#2860
This was a good idea, but in practice the CoreOS pipeline implements a
more sophisticated version of it which include list splitting. We could
try to upstream that, but in the meantime, this is only used by one
upstream CI right now (cosa's), so we'll just inline it there.

The reason for this is that it uses `cosaCmd` and `cosaDir`, both things
I'm trying to get rid of.
Projects are now expected to be built in a separate pod (likely
provisioned with `buildPod`) instead of building code directly in the
cosa pod.
Support for the cosa directory being different from the working
directory makes implementation details messier.

Drop support for it.

Callers can still have their cosa directories be different from the
Jenkins workspace by first wrapping calls to the cosa APIs here in a
call to `dir(cosaDir)`:

```
dir(cosaDir) {
        cosaBuild(skipKola: true)
        kola()
        kolaTestIso(skipMetal4k: true)
}
```

The cosa directory currently needs to be a subdirectory of the workspace
(see coreos#124).
@jlebon
Copy link
Member Author

jlebon commented Oct 17, 2022

This requires migrating all users away from cosaDir and the other removed functionality. This should be straightforward for upstreams which have already adapted the model of building in buildPod, stashing the build, then building FCOS in a cosaPod.

Copy link
Member

@dustymabe dustymabe left a comment

Choose a reason for hiding this comment

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

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants