stopalopa on master
[maven-release-plugin] prepare … [maven-release-plugin] prepare … (compare)
stopalopa on plugin-management-parent-pom-0.1-alpha-11
[maven-release-plugin] prepare … (compare)
stopalopa on master
[JENKINS-57864] Fix failed unit… Merge pull request #67 from sto… (compare)
I’m looking at script-security 1.58
Do you guys know why the hashes here:
don’t match the hashes for it here:
It doesn’t look like the manifest contains that information either, so I’m not even really sure how to check for plugin integrity...
In the plugin folder, it seems like the right plugin and version are getting downloaded, but there’s just something wrong with either the plugin or how Jenkins is trying to find plugins that is causing those errors
"--available-updates" is not a valid option Exception in thread "main" java.io.IOException: Failed to read command-line arguments at io.jenkins.tools.pluginmanager.cli.Main.main(Main.java:21) Caused by: org.kohsuke.args4j.CmdLineException: "--available-updates" is not a valid option at org.kohsuke.args4j.CmdLineParser.parseArgument(CmdLineParser.java:497) at io.jenkins.tools.pluginmanager.cli.Main.main(Main.java:17)
couple of questions about the things I’m supposed to get done this week and how to prioritize:
Make sure to merge and release the work which have not been integrated yet. Please prioritize it over adding new features to your projects
PR #61 was supposed to be an optimization, and theoretically not including it should result in having the same behavior as the original install-plugins.sh. It ended up being more tricky than I realized, so I’m inclined to ignore this for now. However, I’m not sure why @casz was getting so many dependency errors. It seemed like things are working for me. @casz or @slide, would you mind seeing if the latest release is working for you?
Students evaluation submission should include a link to the page which summarizes all contributions. It is highly recommended to use your project pages on https://jenkins.io/projects/gsoc/ as a submission. Please make sure to update them to reflect the final state, to link your blogposts and presentations, and to link the code you have written during GSoC
There will be Jenkins Online Meetups with final demos. The format is similar to what we had. We will conduct the meetings in Zoom, I plan to publish the announcements by Tuesday
Presentation slots: Aug 23, 2:00-3:30PM UTC && Aug 26, 3:00-4:30PM UTC
Please update your presentation abstracts here
We expect all students to publish blogposts summarizing their work over Phase 2 and 3. It is preferable to have technical blogposts announcing new features released during these phases. If you have not already done that, please make sure to submit the drafts this week
Another question I have is about what I should present for the phase 3 evaluations - it seems like the past couple weeks I’ve been working on writing unit tests and cleaning things up, so I don’t have a lot of new features to really demo. Should I talk about my experience at DevOps world? Or should I just talk about how I added unit tests and other fixes?
Then my last question is if I should actually do the first real release? (Contingent on if the plugin dependency is actually working) Can you think of anything else that should be cleaned up or fixed before doing this?