by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Abhishek Gautam
@gautamabhishek46
Aug 13, 2018 4:39:55 PM hudson.ExtensionFinder$Sezpoz _find
WARNING: Failed to load hudson.ExtensionFinder$GuiceFinder
java.lang.InstantiationException: com.google.inject.CreationException: Unable to create injector, see the following errors:

1) Could not find a suitable constructor in jenkins.model.Jenkins. Classes must have either one (and only one) constructor annotated with @Inject or a zero-argument constructor that is not private.
  at jenkins.model.Jenkins.class(Jenkins.java:302)
  while locating jenkins.model.Jenkins
    for field at jenkins.model.Jenkins$EnforceSlaveAgentPortAdministrativeMonitor.j(Jenkins.java:1253)
  at hudson.ExtensionFinder$GuiceFinder$SezpozModule.configure(ExtensionFinder.java:508)

2) Could not find a suitable constructor in jenkins.model.Jenkins. Classes must have either one (and only one) constructor annotated with @Inject or a zero-argument constructor that is not private.
  at jenkins.model.Jenkins.class(Jenkins.java:302)
  while locating jenkins.model.Jenkins
    for field at jenkins.security.s2m.AdminCallableMonitor.jenkins(AdminCallableMonitor.java:33)
  at hudson.ExtensionFinder$GuiceFinder$SezpozModule.configure(ExtensionFinder.java:508)

3) Could not find a suitable constructor in jenkins.model.Jenkins. Classes must have either one (and only one) constructor annotated with @Inject or a zero-argument constructor that is not private.
  at jenkins.model.Jenkins.class(Jenkins.java:302)
  while locating jenkins.model.Jenkins
    for field at jenkins.security.s2m.MasterKillSwitchConfiguration.jenkins(MasterKillSwitchConfiguration.java:18)
  at hudson.ExtensionFinder$GuiceFinder$SezpozModule.configure(ExtensionFinder.java:508)
Abhishek Gautam
@gautamabhishek46

@gautamabhishek46 You have not created a pull request to the submission page yet. Any ETA? It may take a while to get it reviewed, and the deadline is tomorrow

@oleg-nenashev Pull request created

Oleg Nenashev
@oleg-nenashev
@gautamabhishek46 Note that https://speakerdeck.com/gautamabhishek46/yaml-as-pipeline-gsoc-2108-phase-3-evaluation still references July 12, 2018 on the second slide. I would really recommend to review it with mentors before the presentation
Unfortunately I have no time for deep reviews today
Abhishek Gautam
@gautamabhishek46
I will fix that
there is a problem while installing JCasC plugin
image.png
I as getting above errors because of that only I think.
Oleg Nenashev
@oleg-nenashev
I cannot say anything without startup logs
Martin d'Anjou
@martinda
I am looking for the 2nd phase presentation, but this https://jenkins.io/projects/gsoc/2018/simple-pull-request-job-plugin/ has not been updated...
Oleg Nenashev
@oleg-nenashev
@martinda jenkins-infra/jenkins.io#1710, submitted 24 minutes ago
Martin d'Anjou
@martinda
For comparison with 3rd phase
Oleg Nenashev
@oleg-nenashev
I'd guess there are only few changes
Martin d'Anjou
@martinda
This link is broken https://jenkins.io/blog/2018/05/14/simple-pull-request-plugin, I have seen it before, so it's just the link, I will try to find it.
Abhishek Gautam
@gautamabhishek46
Martin d'Anjou
@martinda
@gautamabhishek46 thanks, if you could add the links to all three blog posts that will be useful.
Oleg Nenashev
@oleg-nenashev
@gautamabhishek46 Towards the meeting today, did you have a chance to go through this thread? https://news.ycombinator.com/item?id=17558611
Abhishek Gautam
@gautamabhishek46
@oleg-nenashev no I have not. I will take a look at it before the meeting.
Oleg Nenashev
@oleg-nenashev
ok
Abhishek Gautam
@gautamabhishek46
@martinda links to Phase 1 and Phase 2 blog post are there, link to Phase 3 blog post will be added after jenkins-infra/jenkins.io#1702 will be merged
Oleg Nenashev
@oleg-nenashev
@gautamabhishek46 it may not happen before the end of GSoC. I would recommend to put a pull request link at least
Abhishek Gautam
@gautamabhishek46
:+1:
Kristin Whetstone
@kwhetstone
Sorry I was in a work meeting until now, and I've joined. I hope I didn't miss anything
Abhishek Gautam
@gautamabhishek46
We have our weekly meet at 10:30, are we meeting ?
Martin d'Anjou
@martinda
@gautamabhishek46 do you need a meeting today?
Abhishek Gautam
@gautamabhishek46
It will be great to close pull requests and to decide the final name of the plugin
Martin d'Anjou
@martinda
agreed. We're scheduled to meet in about 30 minutes from now.
Abhishek Gautam
@gautamabhishek46
yes
Martin d'Anjou
@martinda
@kwhetstone @grandvizier @oleg-nenashev @gautamabhishek46 if you are available the SPRP meeting is on in 30 minutes. In the mean time -> food.
grandvizier
@grandvizier
yeah, agreed that meeting in 30 minutes makes sense
Abhishek Gautam
@gautamabhishek46
yes I am available :+1:
Kristin Whetstone
@kwhetstone
Sounds good to me!
Abhishek Gautam
@gautamabhishek46
@/all @grandvizier and me are in the room https://jenkins.io/hangout waiting ...
Martin d'Anjou
@martinda
We are trying to come up with a better name for the plugin. Here is where we are now:
  • Plugin name: yaml-pipeline-builder
  • File name: jenkins-build.yaml
  • Long name: YAML Pipeline Builder
We need to modify past blog posts, and change the github repository name.
Martin d'Anjou
@martinda
The process: for the next releases:
  • do alpha-3 with current feature set
  • change plugin name, do alpha-4
  • do the name changes in the blog posts and documentation as per JENKINS-52663
  • do other changes as required
  • a 1.0-rc-1 release
Abhishek Gautam
@gautamabhishek46
@/all We will have retrospective on Wednesday meeting.
Martin d'Anjou
@martinda
@/all we will send a doodle for the retrospective, not all of us can make it on Wed.
Martin d'Anjou
@martinda
@oleg-nenashev we need someone with lots of powers to approve jenkins-infra/jenkins.io#1702, @grandvizier and I are not that powerful.
Oleg Nenashev
@oleg-nenashev
Do you approve the content?
Martin d'Anjou
@martinda
Jeff and I already approved. The name changes will come after.
Oleg Nenashev
@oleg-nenashev
@martinda the problem is that none of the changes since Jul 12 have been released
I would expect a release to happen first, alpha or RC
Martin d'Anjou
@martinda
@gautamabhishek46 is supposed to do one alpha-3 release using the current code.
At the meeting, we determined that we're still in alpha release cycles.
Oleg Nenashev
@oleg-nenashev
Ok, i will merge the blogpost once the release is cut. Does it work for you @gautamabhishek46 @martinda ?
Martin d'Anjou
@martinda
Agreed. We missed that at the meeting.