[JIRA] (JENKINS-60273) Build Now link on the Edit or Console Output page

2019-11-25 Thread rvern...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rares Vernica created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60273  
 
 
  Build Now link on the Edit or Console Output page   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 _unsorted  
 
 
Created: 
 2019-11-25 19:14  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Rares Vernica  
 

  
 
 
 
 

 
 During the job creation process, I spend a lot of time tweaking the Build > Execute shell steps. I make small edits and then I run the job to see if it worked. I end up needing three tabs open: 
 
Edit job 
Trigger Build Now 
Console output 
 It would be nice to have a Build Now link on the job edit page or on the console output page. This way I can get away with two tabs.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  

[JIRA] (JENKINS-60272) Stuck on Installing Plugins/Upgrades

2019-11-25 Thread rvern...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rares Vernica created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60272  
 
 
  Stuck on Installing Plugins/Upgrades   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 update-sites-manager-plugin  
 
 
Created: 
 2019-11-25 18:37  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Rares Vernica  
 

  
 
 
 
 

 
 See bellow for what I did. It has been like this for more that 10 minutes. Installing Plugins/Upgrades 
 

 
 
Preparation 

 
Checking internet connectivity 
Checking update center connectivity 
Success 
  
 
 
LDAP 
 Downloaded Successfully. Will be activated during the next boot 
 
 
Pipeline: Stage Tags Metadata 
 Downloaded Successfully. Will be activated during the next boot 

[JIRA] (JENKINS-23786) Permit "Execute shell" jobs to return 2 for "unstable"

2019-07-16 Thread rvern...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rares Vernica commented on  JENKINS-23786  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Permit "Execute shell" jobs to return 2 for "unstable"   
 

  
 
 
 
 

 
 See this screenshot on how you can set it. Notice the Exit code to set build unstable field.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.156174.1405394642000.12508.1563294361329%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-23786) Permit "Execute shell" jobs to return 2 for "unstable"

2019-07-16 Thread rvern...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rares Vernica updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-23786  
 
 
  Permit "Execute shell" jobs to return 2 for "unstable"   
 

  
 
 
 
 

 
Change By: 
 Rares Vernica  
 
 
Attachment: 
 exit-unstable.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.156174.1405394642000.12506.1563294361309%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-26640) svn: E175002: handshake alert: unrecognized_name

2018-09-19 Thread rvern...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rares Vernica commented on  JENKINS-26640  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: svn: E175002: handshake alert: unrecognized_name   
 

  
 
 
 
 

 
 Ivan Fernandez Calvo I think the issue is with the updates.jenkins.io certificates. See note in the error trace.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-26640) svn: E175002: handshake alert: unrecognized_name

2018-09-18 Thread rvern...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rares Vernica commented on  JENKINS-26640  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: svn: E175002: handshake alert: unrecognized_name   
 

  
 
 
 
 

 
 Setting -Djsse.enableSNIExtension=false fixes the Subversion checkout error, but introduces a new error when initally starting Jenkins. The new error is: 

 

ci_1 | javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: No subject alternative DNS name matching updates.jenkins.io found.
ci_1 | at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
ci_1 | at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1964)
ci_1 | at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:328)
ci_1 | at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:322)
ci_1 | at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1614)
ci_1 | at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:216)
ci_1 | at sun.security.ssl.Handshaker.processLoop(Handshaker.java:1052)
ci_1 | at sun.security.ssl.Handshaker.process_record(Handshaker.java:987)
ci_1 | at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1072)
ci_1 | at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1385)
ci_1 | at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1413)
ci_1 | at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1397)
ci_1 | at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:559)
ci_1 | at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185)
ci_1 | at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1564)
ci_1 | at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492)
ci_1 | at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:263)
ci_1 | at hudson.model.DownloadService.loadJSON(DownloadService.java:167)
ci_1 | at hudson.model.UpdateSite.updateDirectlyNow(UpdateSite.java:185)
ci_1 | at hudson.model.UpdateCenter.updateDefaultSite(UpdateCenter.java:2185)
ci_1 | at jenkins.install.SetupWizard.init(SetupWizard.java:179)
ci_1 | at jenkins.install.InstallState$InitialSecuritySetup.initializeState(InstallState.java:164)
ci_1 | at jenkins.model.Jenkins.setInstallState(Jenkins.java:1039)
ci_1 | at jenkins.install.InstallUtil.proceedToNextStateFrom(InstallUtil.java:97)
ci_1 | at jenkins.install.InstallState$Unknown.initializeState(InstallState.java:82)
ci_1 | at jenkins.model.Jenkins$17.run(Jenkins.java:3201)
ci_1 | at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)
ci_1 | at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296)
ci_1 | at jenkins.model.Jenkins$5.runTask(Jenkins.java:1068)
ci_1 | at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214)
ci_1 | at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
ci_1 | at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
ci_1 | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
ci_1 | at java.lang.Thread.run(Thread.java:748)
ci_1 | Caused by: java.security.cert.CertificateException: No subject alternative DNS name matching updates.jenkins.io found.
ci_1 | at sun.security.util.HostnameChecker.matchDNS(HostnameChecker.java:214)
ci_1 | at sun.security.util.HostnameChecker.match(HostnameChecker.java:96)
ci_1 | at sun.security.ssl.X509TrustManagerImpl.checkIdentity(X509TrustManagerImpl.java:455)
ci_1