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

4.x <- Full revision of Jenkins Pipelines, to make them work again #807

Merged
merged 38 commits into from
Jun 7, 2022

Conversation

victorpablosceruelo
Copy link
Contributor

@victorpablosceruelo victorpablosceruelo commented May 18, 2022

The upgrade of the atlassian stack needed some modifications in quickstarters because some bugs appeared.

Tasks:

Copy link
Member

@cschweikert cschweikert left a comment

Choose a reason for hiding this comment

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

Hi everybody, I don't know the background of this change, but since it claims to remove usage of Java 17, the removal should rather be clean and complete. In common/jenkins-agents/maven/docker/Dockerfile.centos7 I can still find yum install ... java-17-... and calling of use-j17.sh, which again I'd rather delete then breaking each line with exit 1. If java 17 should come back at a later point in time, there is still the git history, release tags, etc. with this code.

CHANGELOG.md Outdated
@@ -35,6 +35,7 @@
- ODS AMI build failing due an E2E test error of ionic quickstarter ([#742](https://github.com/opendevstack/ods-quickstarters/issues/742))
- ODS AMI build failing due an missing list of supported browsers in ionic quickstarter ([#756](https://github.com/opendevstack/ods-quickstarters/issues/756))
- inf-terraform-aws: Fix error handling of Makefile ([#680](https://github.com/opendevstack/ods-quickstarters/issues/680))
- Removes jcenter repositories and jdk-17 usage ([#807](https://github.com/opendevstack/ods-quickstarters/pull/807))
Copy link
Member

Choose a reason for hiding this comment

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

isn't this also a breaking change? If so I'd move this entry to ### Modified. Also I'd rename to - Remove JCenter repositories and jdk 17 support ... or so

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I've changed it. It was an initial message. Now it is better explained.
Do you see it ok now?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes. You're right. It was a breaking change.
But we found a different solution that keeps jdk 17, using Adoptium Temurin, maintained by Eclipse.
More information in the following link:
#808

@stitakis
Copy link
Member

Hi all, I not agree on removing JDK 17 support without first exploring a way to solve the idk 17 installation problem in centos 7. Was this tried out? Another observation, the title of this ticket does not match to the changes. This shouldn't be the case.

Copy link
Member

@stitakis stitakis left a comment

Choose a reason for hiding this comment

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

Before reverting the support of jdk 17 I suggest to try to solve the installation problem in centos first.

@victorpablosceruelo
Copy link
Contributor Author

Fixed the problem with JDK 17, so support of JDK 17 is back.
Fixed some other problems in docker images generation and pipelines.
Generated AMI image, so everything is working right now.

@victorpablosceruelo victorpablosceruelo changed the title Task/upgrade atlassian stack 4.x <- Task/upgrade atlassian stack Jun 1, 2022
Copy link
Member

@cschweikert cschweikert left a comment

Choose a reason for hiding this comment

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

I reviewed some of the changes again. Unfortunatelly I'm having problems understanding the reasoning of some of these changes (e.g. removal of jcenter). Also some of the changes don't seem to be related to the initial description of the PR (e.g. about nodejs12 and terraform). For those it might make sense to move them over into a new issue+PR. Also it would be good to have an issue that this PR is directly based on (e.g. "Full revision of Jenkins Pipelines, to make them work again" seems to point to an issue).

Thanks @victorpablosceruelo for all the work you put into this PR. Seems like you needed to try a lot of crazy stuff to get it running.

@victorpablosceruelo victorpablosceruelo changed the title 4.x <- Task/upgrade atlassian stack 4.x <- Full revision of Jenkins Pipelines, to make them work again Jun 2, 2022
@victorpablosceruelo
Copy link
Contributor Author

Hi @cschweikert
Thanks for your comments.
You are right. The PR title is not valid anymore. I changed it.
Besides, I added extra information on what are the bugs or issues we achieve with this PR.
Hope you like it a little bit more now
Thanks !!!

@victorpablosceruelo victorpablosceruelo dismissed cschweikert’s stale review June 7, 2022 08:33

I did the changes requested, but GitHub says I did not do them. :S

@victorpablosceruelo victorpablosceruelo removed the request for review from cschweikert June 7, 2022 08:34
Copy link
Member

@cschweikert cschweikert left a comment

Choose a reason for hiding this comment

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

@victorpablosceruelo THX again for bringing this complex topic forward 😀

@victorpablosceruelo
Copy link
Contributor Author

Thanks @cschweikert for your comments.

I'm getting the following error in GitHub:
The base branch restricts merging to authorized users.
(https://docs.github.com/articles/about-protected-branches/)

I do not Know what to do at this point...

@cschweikert
Copy link
Member

yeah, 4.x is a protected branch that only project admins can merge into. Maybe @michaelsauter or @braisvq1996 can help here 😊

@BraisVQ BraisVQ merged commit 3b79d1d into 4.x Jun 7, 2022
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.

5 participants