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

Move node/npm download root to properties to allow easy override #434

Merged
merged 1 commit into from
Sep 9, 2021

Conversation

Vlatombe
Copy link
Member

@Vlatombe Vlatombe commented Sep 9, 2021

  • Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
  • Ensure that the pull request title represents the desired changelog entry
  • Please describe what you did
  • Link to relevant issues in GitHub or Jira
  • Link to relevant pull requests, esp. upstream and downstream changes
  • Ensure you have provided tests - that demonstrates feature works or fixes the issue

@Vlatombe Vlatombe requested a review from jglick September 9, 2021 12:00
Copy link
Member

@dwnusbaum dwnusbaum left a comment

Choose a reason for hiding this comment

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

Are the current URLs are broken for any OSS plugins that are using frontend-maven-plugin? Should we update them to something else?

@Vlatombe
Copy link
Member Author

Vlatombe commented Sep 9, 2021

OSS infrastructure is flaky since some jfrog saas update apparently, and ideally in CloudBees we'd like to use a different mirror to avoid pegging the OSS infrastructure.

@timja
Copy link
Member

timja commented Sep 9, 2021

Is there any context to the why of this PR?

i.e. why does this need changing?


I see the above, and yes our builds are getting hit by it too 😢, random connection time outs, and content-length not matching / premature end of something error

@dwnusbaum
Copy link
Member

dwnusbaum commented Sep 9, 2021

OSS infrastructure is flaky

Ah, ok, I thought that these URLs were failing consistently. When I checked locally with curl, it looked like the problem was that the download links created by frontend-maven-plugin actually downloaded an HTML page that would run JavaScript to initiate the download if you were using a web browser, but maybe that's not always the case.

@timja
Copy link
Member

timja commented Sep 9, 2021

OSS infrastructure is flaky

Ah, ok, I thought that these URLs were failing consistently. When I checked locally with curl, it looked like the problem was that the download links created by frontend-maven-plugin actually downloaded an HTML page that would run JavaScript to initiate the download if you were using a web browser, but maybe that's not always the case.

they are doing user agent sniffing, it's really annoying.

curl should get actual files, but powershell does not.
We had to change the jenkins docker images to pretend to be curl so that our windows agent images could fetch remoting.

@jtnord jtnord merged commit 54649fa into jenkinsci:master Sep 9, 2021
@jtnord
Copy link
Member

jtnord commented Sep 9, 2021

I can not deploy this at the moment despite using my reset password. not sure if it is something for my account or more generally that deployments are still not working.

@timja
Copy link
Member

timja commented Sep 9, 2021

I can not deploy this at the moment despite using my reset password. not sure if it is something for my account or more generally that deployments are still not working.

I was able to release junit a couple of days ago after downloading a settings.xml from artifactory with either an encrypted password or api token in it (not very clear)

you can either try that or I can release it if you want?

@jtnord
Copy link
Member

jtnord commented Sep 10, 2021

@Vlatombe Vlatombe deleted the npm-repo branch September 10, 2021 08:01
@Vlatombe
Copy link
Member Author

@jtnord you should have permission now.

@jglick
Copy link
Member

jglick commented Sep 10, 2021

Or if you want me to cut a release, just LMK.

I have not yet tried to set this repo up for JEP-229 or even JEP-305 out of concern that https://www.mojohaus.org/flatten-maven-plugin/flatten-mojo.html#flattenMode is not configured correctly for the POM use case. It does work fine on bom so it is probably safe here too but needs some careful testing.

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

Successfully merging this pull request may close these issues.

6 participants