Bugzilla – Full Text Bug Listing
| Summary: | Switch off GEF Travis CI Build | ||
|---|---|---|---|
| Product: | [Tools] GEF | Reporter: | Tamas Miklossy <miklossy> |
| Component: | RelEng | Assignee: | Nobody - feel free to take it <nobody> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | 5.3.2 (2020-12) | ||
| Hardware: | PC | ||
| OS: | Windows 10 | ||
| See Also: | https://bugs.eclipse.org/bugs/show_bug.cgi?id=558971 | ||
| Whiteboard: | |||
|
Description
Tamas Miklossy
Removing Travis CI should be fairly straightforward. Removing the travis.yml file will make Travis ignore this repository. No more builds will be started or required. However, the GEF repository might still be "integrated" with Travis CI. You'd need to be a repository admin (which I am not) to add or remove those integrations. I am not sure, if just ignoring the integration is an okay move for us. Do we know who actually is an admin for this repository? Additionally, we might want to setup a multibranch job to run on JIRO so that branches (!=master) and PRs are still tested. Since the current gef-master job's build numbers play a role in the releasing process, I wouldn't want to touch that one right now. Adding a multibranch job that ignores master, while keeping gef-master as-is, would be my choice for this. WDYT? The Travis Build is currently still pending, while the JIRO Build has already completed successfully. I think it would be enough to build only the GEF master branch on JIRO (since currently we do not have any other branches or PRs that also need to be built). Later on (on demand), we can still setup a multibranch job to run on JIRO so that branches (!=master) and PRs are still tested. @Nico Prediger: as suggested, could you please remove the travis.yml file from the git repository and establish a connection between GitHub and JIRO, so that whenever a commit on the master branch can or cannot be built on JIRO, the result of the build should be also visible on GitHub. Would be nice if we could fix this for GEF 5.3.2 (2020-12), that is planned to be released on 16.12.2020. > See also https://github.com/xtext/xtext-gradle-plugin/issues/176 Why is that relevant if we want to disable it anyway? > @Nico Prediger: as suggested, could you please remove the travis.yml file from the git repository Done: https://github.com/eclipse/gef/pull/98 > and establish a connection between GitHub and JIRO The best way to feed back build results would be to use a GitHub Organization style Jenkins job. This one can (but does not need to) build all branches and PRs. And it will automatically set a commit status for every built commit. BUT: I cannot change the current gef-master job into a GitHub Org. style job. I would have to recreate it, which would somewhat break the current release process because it relies on the numbers. There are other (uglier) ways, like using curl to directly talk to GitHub API, but I don't want to do this. However we end up doing this, we'll need to create authentication tokens (which I cannot do). Thanks for the info Nico! First of all, we should focus on switching the Travis Build off. About the integration of GitHub and JIRO we can take care of later. Resolving as fixed in 5.3.2 (2020-12). |