https://doodle.com/poll/edepxx6g9w4izzir?utm_source=poll&utm_medium=link -> here's the doodle poll for picking a time for the presentation
1 reply
I have submitted the work (GitHub repository) and the student evaluation.
I am not sure what I should add in GSoC final presentation PPT..
I changed the next steps part (easy) and new features could be demoed..
Can we add anything else in the PPT?
Got it! I will add that. Would it be okay to write steps to add a package/project type... Eg.
- Add the type in the factory class
- Create a public class...
Yes I think big picture steps are enough, just to help potential contributor where to look at
1 reply
too much documentation is not always a good idea as it has to be maintained, and outdate documentation is really bad
Woops.. The CD failed :(
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project conventional-commits: Failed to deploy artifacts: Could not transfer artifact io.jenkins.plugins:conventional-commits:hpi:0.7.3 from/to maven.jenkins-ci.org (https://repo.jenkins-ci.org/releases/): authentication failed for https://repo.jenkins-ci.org/releases/io/jenkins/plugins/conventional-commits/0.7.3/conventional-commits-0.7.3.hpi, status: 401 Unauthorized -> [Help 1]
Hello @MarkEWaite, No, It isn't the first run and yeah we are using automated CD, which is exactly why I was surprised at it failing 😅
Hi all, just starting the issue #81 and I have a question : I'm less familiar with gradle than maven, for me there is non command line to write back to the build.gradle sot I write the next version with Java code . Is it ok for you or did I miss a magic gradle option ? 😉
3 replies
I haven't been around a lot and I am sorry for that. I wanted to let y'all know -- I just graduated (didn't even get a farewell thanks to covid :/ ). A lot of my time was invested in looking for a job and simultaneously apply for Masters (next fall). I would really like to take some time for masters applications. So, the frequency of contribution would be low for some time. 😅
3 replies
Hi (again :wink:), do you think that we'll must update maintenaires members (I don't know if I have the level but I can help for this role if you want). And another question : do you think this plugin can be proposed to hacktoberfest or we don't have enough issues ?
2 replies
Thanks for yours answers, I'll try the process to join the maintainers list ! For hacktoberfest I think that will be a good "boost" for the project, I'll try this week-end to create issues and read how to propose this project to hacktoberfest 😉
Before i request the access I see there is another maintainers (I didn't know there is already 5 maintainers), is it ok for you @garethjevans , olblak , @kwhetstone and @Dohbedoh that I do this kind of demand. The goal was to help the plugin to live as kuro has less time but perhaps you are enough as maintainers ?
as I've no response I'll try to propose my PR to became maintainer of the plugin 😉
Stéphane Philippart: I support you as maintainer, we are maintainers because we were Gsoc maintainer helping kuro
Hi (again 😉), in addition of the IT and UT in the project I want to test in a real Jenkins instance the plugin. I have a local instance on my laptop but I'm wonder if it exist a centralize instance where we can do such tests ?
Hi Stephane, I don't think we provide that, maybe @MarkEWaite knows more about that
1 reply
another question (sorry for my noob questions) : the 0.7.3 release has several features or bugs, the last release 0.7.4 that has only the last PR that I merge. how regroup several PR in a release ?
I've checked the github action and I saw that if the draft release has feat / bug entries the release is automatically fired. If I understand well this release (0.7.3) has several entries because the previous build phase exit with error status ?
Apparently it's the same explanation for the 0.4.0 : the release stage is on error until that it was success and get the previous merged PR.
I've checked the github action and I saw that if the draft release has feat / bug entries the release is automatically fired. If I understand well this release (0.7.3) has several entries because the previous build phase exit with error status ?
Apparently it's the same explanation for the 0.4.0 : the release stage is on error until that it was success and get the previous merged PR.
Once releases are published, you can go back :) (at least not a good practice) considering that releases are automated, you can't regroup PR for a specific release
Better to have a PR that solve a specific problem which can be merged as soon as possible
agree with you, it's just to avoid multiple releases and group features when there no urgency 😉, but it's cool I prefer automation vs manual !
Yep unfortunately we can't have everything :D most of the time, I also prefer automation :D
Yes, I think we are interested, regarding items being well suited, I am not sure for first time contributors...
I propose this:
I propose this:
- Add more project types (Go, Scala, etc)
- WriteVersion for remaining project types (Python, Make, etc)
- Unit tests wherever needed
I'll just to take time to create issues this week-end 😉
hi all, just added some few issues (with label good first issue to help to for newcommers) and added the hacktoberfest label 😉. Is there another thing to do for hacktoberfest compliant ?
I added Hacktoberfest label to issues as the documentation explain it : https://hacktoberfest.digitalocean.com/resources/maintainers
Hi, is there any rules for the topics on the github repository ? When I look other plugins it's seems quite open 😉
Talk at DevOps world was live some time back, got some nice questions and suggestions in the QnA... so I thought I will share here..
Q. Does this plugin support generic VERSION file which maintains the semver? We adopted that to keep a single source of truth for version info that is used by Jenkinsfile, makefile, git-tags etc Thanks! ( @SohamJ asked this)
- I feel this can be done, maybe another optional parameter? Thoughts?Stéphane Philippart , @garethjevans
7 replies
Is there a preferred contributing.md format/template used in jenkins? (I saw different styles in various projects but would like to confirm)
If there isn't then I think this looks good (jenkinsci/conventional-commits-plugin#121) for the conventional commits plugin
If there isn't then I think this looks good (jenkinsci/conventional-commits-plugin#121) for the conventional commits plugin
1 reply
kuroto have o contribution page for Hacktoberfest I think we can merge
I just ask to the committer to add a link in the README file and link the generic CONTRIBUTING