I've merged jenkins-infra/jenkins.io#4509 so that the blog post can be linked in your report @arpoch
@arpoch https://youtu.be/sEqK4dAFg4s is the final presentation. Slides are at https://docs.google.com/presentation/d/1rAjjF_pBjtGDaaC8rgReqVzd9WJ4Z0jZTvaPHabk3SI/edit#slide=id.p . Project page is https://www.jenkins.io/projects/gsoc/2020/projects/git-plugin-performance/
8 replies
@MarkEWaite , @rishabhBudhouliya , @justinharringa:matrix.org , the link of slides for CDF-GSoC-21 final evaluation:
https://docs.google.com/presentation/d/1oVjwKt4OsxxDWs4eY3JL6jNxi2YyY9IQNizws-EAITM/edit?usp=sharing
https://docs.google.com/presentation/d/1oVjwKt4OsxxDWs4eY3JL6jNxi2YyY9IQNizws-EAITM/edit?usp=sharing
@arpoch From a cursory view, it looks great. I know you've done great work this summer and you are directly outlining it in your presentation.
I do have some comments which are optional and my personal opinion:
I do have some comments which are optional and my personal opinion:
- When I was coming up with the final presentation, I always wondered how to make the presentation more palatable to the general audience. I believe thinking like a salesman works. Make the product as simple as you can to sell it.
- We all know you've done a project on credentials binding for the git plugin, why have you done it and what does it mean? You could mention that it the presentation intro if you'd like. Some people might not remember the motivation of the project explain during the phase 1 presentations.
- It's hard and often times superflous, but I like to attach a bigger meaning to the project. Something along the lines of ~providing convenience to the Jenkins user~ or ~more freedom of choice to the pipeline users~.
- Git plugin is one of the most used plugin in the ecosystem, the checkout step is probably used by everyone using a Jenkins pipeline. Even a small feature means a lot to the community, yours is a big one, sell it like that.
Also, I think I made a mistake by naming the title of the presentation = the name of the project. Everyone knows the name of the project. The title should be what you want to sell. The meaning of the project.
1 reply
On the road ahead you mention "test units" where I think you mean to say "unit tests" but I could be misunderstanding intent 😃
2 replies
@MarkEWaite , @justinharringa:matrix.org , @rishabhBudhouliya , I dont know why I didn't gave attention to this before even though I knew that it was coming. The Github support for password authentication has been completely discontinued, although I am using gitlab vcs now to demo my project work.
As developer I am curious to know that does Jenkins credentials Plugin support access Token, from what I have investigated it dose not, I have seen workarounds of using Username/Password credential as access token.
I think the Username and Password binding should include support for access tokens since password based auth are not that secure and seems to be deprecated in the coming future.
3 replies
Not going to be able to make the presentation but I'm sure it's going to go great! Nice work @arpoch !
1 reply
If either of you need an account in the future, let me know, and we'll recreate them
Topics on my mind include:
- Strengths and weaknesses of current implementation (strong: private key support on Linux, weak: private key support on Windows due to requiring ssh in the path)
- Alternatives for releasing the phase 2 ssh private key implementation
- Testing and other activities needed before merge and release
- Handling issues that may be reported after release (does @arpoch want to be assigned Jira tickets, etc.)
- Should we provide more examples with more details (and possibly close more Jira tickets as a result)?
No worries. I probably won't be able to make Friday as normal but again super appreciative of all the good work!
Meeting has started at https://zoom.us/j/94941068245?pwd=MDdiVFZuckpUbC9zOXVjNzVRNFVRdz09 .
Sorry about that @arpoch . Had a personal meeting 30 minutes prior, then got involved writing tests for the Jenkins installers
Would you be willing to update the pull request to use the newer library?
Currently we are depending upon sshd transitive dependency, so are you suggesting on using the sshj library instead of sshd?
Hi @MarkEWaite , I was checking out the 2022 GSoC ideas discussion page and I'd like to discuss this particular idea: https://community.jenkins.io/t/google-summer-of-code-gsoc-2022-call-for-organizers-mentors-and-project-ideas/1010/7?u=rishabhbudhouliya
git maintenance is supposed to optimise existing git repo and speed up git operations. Do we have any data to validate the decrease in operation time and how this would be beneficial for the git plugin and its users? If not, would we include a benchmarking experiment as an expectation in the gsoc proposal for this idea?
https://issues.jenkins.io/browse/JENKINS-13493 includes a report of detectable performance improvements after garbage collection of a long-lived cache repository. I'm not worried about having the rigor of a benchmark inside the plugin because the performance loss is due to the git tool (both command line git and JGit), not due to code in the plugin. I saw performance improvements on ci.jenkins.io as well.
Yes, that's a larger than typical repository. 5+ years ago I was regularly handling a git repository that was 20 GB. It was a painful example of poor decisions on what to include in the repository. It was still useful to us, even though its size made it much less useful than it could have been
Hi all, I found a bug in the Jenkins Git plugin where tags are not checked out unless you clone the project twice. More than a month ago I filed a JIRA ticket: https://issues.jenkins.io/browse/JENKINS-67984 with details on how to reproduce the bug. Can anyone help me with pointers please?
@Hrushi20 and @rishabhBudhouliya, I've placed the Git Cache Maintenance meeting recordings at https://community.jenkins.io/t/git-cache-maintenance-gsoc-2022/2563#git-cache-maintenance-meeting-recordings-1
