Skip to content

Jenkins#190

Merged
jburel merged 44 commits into
ome:masterfrom
jburel:jenkins
Mar 4, 2022
Merged

Jenkins#190
jburel merged 44 commits into
ome:masterfrom
jburel:jenkins

Conversation

@jburel

@jburel jburel commented Feb 9, 2022

Copy link
Copy Markdown
Member

This PR updates jenkins to LTS version
Usage of personal branch will be removed when ome/omero-install#261 is merged and enew version available in docker file.

Note: Commits could be squashed since many commits have been made during the investigation

Reference #188

@jburel jburel mentioned this pull request Feb 9, 2022

@sbesson sbesson 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.

A few comments primarily regarding the management of the plugins/Jenkins moving forward. Otherwise the management of the omero-server/omero-web user and the reduction of the omero_install complexity is inline with my understanding of the changes proposed in ome/omero-install#261.

Comment thread home/config.xml
Comment thread jenkins/plugins.txt
matrix-auth:2.3
icon-shim:2.0.3
authentication-tokens:1.3
swarm

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.

So the new strategy is to stop tracking pinned versions of the plugins? From my side that would reduce maintenance but I wonder what the impact will be when breaking changes are made to the plugin. Would this prevent a deployment as the job configuration are not in-sync?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Pinning the version leads to errors again i.e. unable to find plugins etc.
Test:

  • install without pinning
  • run script to get the version of each plugin
  • install with pin version
  • failure

Comment thread server/Dockerfile

@sbesson sbesson 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.

Barring the ongoing question on the plugins versions, the state of the changes looks good to me. It effectively brings Jenkins to the current LTS, simplifies several installation steps and clarifies a few assumptions in the README. Should we get this merged and move towards the deployment of an updated version of merge-ci/latest-ci ?

@jburel

jburel commented Feb 10, 2022

Copy link
Copy Markdown
Member Author

I think we need to agree on modified logic introduced in ome/omero-py#316 and ome/openmicroscopy#6301 since they both have implications on the job configurations.

Note that this PR does not include the change to support ome/omero-documentation#2195.
A cd omero needs to be added to the docs job. I have added manually to the CI but not pushed a commit since we have not validated the doc PR.

Happy to push a commit to that effect.

@sbesson

sbesson commented Feb 10, 2022

Copy link
Copy Markdown
Member

Similarly to the ongoing work on CentOS7/Python 3.8, my vote would be for separating the work on the OMERO documentation hosting by readthedocs at least as a follow-up PR and keep this focused on the Jenkins LTS upgrade.

@jburel

jburel commented Feb 11, 2022

Copy link
Copy Markdown
Member Author

I agree. This was just mentioned for info

@jburel

jburel commented Mar 3, 2022

Copy link
Copy Markdown
Member Author

Merging and proposing to tag 0.16. If any objection
I will send open a PR with change required for python 3.8

@jburel jburel merged commit 09cc575 into ome:master Mar 4, 2022
@jburel jburel deleted the jenkins branch September 19, 2023 08:16
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.

2 participants