Re: Updates to the Blue Ocean plugin and a new Pipeline sub-project

[Ullrich Hafner]

> Am 17.06.2019 um 13:17 schrieb Jeremy Hartley :
> 
> Hello fellow Jenkins users and developers,
> 
> I am a product manager at CloudBees and have taken over responsibility for 
> the Jenkins Blue Ocean sub-project. Over the last year, the teams working on 
> Jenkins at CloudBees have looked at the initiative of overhauling the Jenkins 
> user experience. This analysis led us to conclude that Blue Ocean is a great 
> way to work with Jenkins Pipelines but that it’s not the best way to achieve 
> the larger goal of overhauling the entire Jenkins user experience. 
> 
Does this mean that blue ocean is dead and a new - even bigger - project will 
come? Wouldn’t it make more sense to start with smaller UI refactoring steps in 
the current UI rather than another large overall approach that may fail in the 
end? There is so much potential in the current UI that could be leveraged with 
small effort. (An overall approach still can be started in parallel. But now we 
have the problem that almost nobody is improving the classic UI side anymore 
because of the announcement of blue ocean.)

>  Christina Noren's blog post on CloudBees and Jenkins 
>  gives a good 
> update of the work we are doing at CloudBees on Jenkins overall. The 
> CloudBees teams working on Jenkins are currently engaged in a discovery 
> process to start a large project to modernize the overall user experience in 
> Jenkins. This research goes beyond simple user interface updates and focuses 
> on usability in addition to  modern aesthetics. 


Maybe it would also make sense if you could run such a discussions in public 
(dev list?) so that non-Cloudbees contributors can participate? At least during 
the initialization of blue ocean we had a lot of discussions with plugin 
authors about requirements for a new UI.

> 
> I believe that Pipeline is THE way that continuous integration and continuous 
> delivery are best done in Jenkins. Therefore, I am proposing that we raise 
> Pipeline to become a top-level sub-project within Jenkins.
> 
> Making Pipeline a top-level sub-project will:
> Clearly tie Jenkins to CI/CD for new and existing Jenkins users
> Make it easier for everyone to find documentation for using CI/CD Pipelines 
> in Jenkins
> Help the community and CloudBees to continue to improve and build out new 
> features for Pipeline and to improve documentation and examples
> Help clarify that Blue Ocean is a feature of Jenkins Pipeline
> 
> I look forward to getting your feedback. Thank you for your time.
> 
> Regards
> 
> Jeremy Hartley
> Senior Product Manager
> CloudBees, Inc.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-users+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/264C1702-896E-485B-8630-8B4616607AE3%40cloudbees.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/7D410C5E-5A40-4D3C-8D5E-6C92A8D00DF9%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Need help on Jenkins setup and clearing doubt

[Swarup Kumar Sil]

Hi, I had used Jenkins as an user two years back as a build and deployment 
tool in a past project. But I never installed Jenkins in my system, neither 
I had used any cloud setup. I have to connect the VPN only before 
connecting to Jenkins application. Now I want to configure in the same way 
in my current project. Could you please explain how it was working that 
time and how should I do the same in my current project ? 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/039b8e58-b33b-49ae-a021-38199a94896b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Declarative Pipeline Error : OCI runtime exec failed

[Wolfgang Friedl]

Could you solve the problem?
I run into the same issue.

Regards

Wolfgang

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/032bfb90-5f09-4ce9-b7a9-5d72f9f7adf4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Declarative Pipeline Error : OCI runtime exec failed

[Swarup Kumar Sil]

Not yet.Sent from my Huawei Mobile Original Message Subject: Re: Jenkins Declarative Pipeline Error : OCI runtime exec failedFrom: Wolfgang Friedl To: Jenkins Users CC: Could you solve the problem?I run into the same issue.RegardsWolfgang



-- 
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/032bfb90-5f09-4ce9-b7a9-5d72f9f7adf4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.




-- 
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/-1hgde6krugd7-g1f70e79bw7gz95dbz5x1vm1t11rn3-95747s8qw0bs1bd8qc-ww3f2m-j9dd6g2am2bo-8yld00-5ldosc-dtl7ox-ig0jjb6g5md5-m6xx6p-lh8u9l-qcmoo8v8r3uq7wtyjb7nl59b.1560862043806%40email.android.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins Performance Plugin provides all reporting as a cumulation of all runs, not just the relevant run for the report.

[Stuart Kenworthy]

Produced using:
- Jenkins 1.121.2
- Performance Plugin 3.15
- Plot 2.1.0
- Jmeter 5.1

I have googled, searched this group and search the jenkins issue log and 
cannot find an example of this being recorded but cannot imagine I am the 
only one having this issue.

I may be missing something but looking at the Jenkins Performance Plugin 
"comparison with previous build" graph appears to show the difference 
between the current report and the previous report, however both reports 
are just an accumulation of all runs up until that point which pretty much 
makes any of the reporting provided by the plugin useless.

Say your jmeter script is 10 samplers.Run 1 has 0 failures and run 2 has 
100% failure rate, the report looks like this:

*URI | Samples  | Errors*
Login   | 20 (+10)  | 50% (+50%)

As a comparison to the previous run I would expect it to look like

*URI | Samples  | Errors*
Login   | 10 (10)| 100% (0%)

Say run 3 was again a clean run the report looks like

*URI | Samples  | Errors*
Login   | 30 (+10)  | 33.33% (-16.66%)

Once again as a comparison to the previous run I would expect it to look 
like this as we do not care about the first run in a comparison again the 
previous build:

*URI | Samples  | Errors*
Login   | 10 (10)| 0% (100%)

Note I also did not expect a + or - in the adjusted figure as surely this 
should just contain the last results.

It also appears all the graphs are based on the cumulative figures so the 
never actually represent the run the seem to represent.

Take this graph for example, we were having downstream issues which 
resulted in each run hitting a 98% error rate, the last 2 runs were around 
25% error rate but rather than the percentage of errors dropping to around 
25% to reflect that run, it once again just provides the cumulative error 
rate of all run before it.


Surely it should look like this:
This also breaks things like threshold checking for build failures which 
also uses the cumulative figure.

Deleting runs from jenkins also has unesired effects such as reducing the 
number of samplers in the next report but not previous statistics.

Is there any way to fix this reporting?

Thanks

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/2329c2e2-f3d4-47e5-ab0d-90eebc304f56%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins Kubernetes plugin credentials for Google Kubernetes Engine cluster

[samt88]

I need to setup the Jenkins Kubernetes plugin to fire off slaves on demand. 
The top portion of the plugin requires us to provide two important values 
to the plugin. One is the value for the "Kubernetes  URL" field and the 
other is the value for the "Credentials" field. By providing these two 
values and clicking on the "Test Connection" button we should be able to 
verify that Jenkins can successfully connect to the cluster.

The Google Kubernetes Engine does not provide a username/password for 
cluster by default anymore.  The GKE page where we see the cluster 
credentials specifically says "Basic authentication for this cluster is 
disabled". I only see the value for "Cluster CA certificate" on this page.  
Does 
anyone have the step by step instructions on how I can use this certificate 
to configure the "Credentials" field of the Jenkins Kubernetes plugin to 
connect to the cluster? I have tried a few combinations but I have not been 
successful so far. Thanks.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/1149bb3a-0063-4b0f-8376-8f5a0071a6f7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Error Message : org.xmlpull.v1.XmlPullParserException: only 1.0 is supported as

[YUQI ZHANG]

I came across the same problem when I upgrade jenkins first then downgrade 
it . 

my solution here hopes could help someone: 

1. service jenkins stop 
2. mv JENKINS_HOME/config.xml JENKINS_HOME/config.xml_bak
3. service jenkins start

then I can use jenkins without authentication.  there are still some 
problems which is not totally fixed

I simply upgrade jenkins again  and recover original config.xml by doing:

mv JENKINS_HOME/config.xml_bak JENKINS_HOME/config.xml

service jenkins restart

finally every job can be built again normally. thanks god. I would never 
trying to do this upgrading/downgrading things without backup!




在 2018年3月3日星期六 UTC+8下午6:23:27，Poovaraj Thangamariappan写道：
>
> Hi Team,
>
> I have downgraded Jenkins latest version to old version(2.48). I got below 
> error message after launch the Jenkins. Please help me to fix this issues.
>
> org.xmlpull.v1.XmlPullParserException: only 1.0 is supported as  not '1.1' (position: START_DOCUMENT seenat org.xmlpull.mxp1.MXParser.parseXmlDeclWithVersion(MXParser.java:2608)
>   at org.xmlpull.mxp1.MXParser.parseXmlDecl(MXParser.java:2592)
>   at org.xmlpull.mxp1.MXParser.parsePI(MXParser.java:2466)
>   at org.xmlpull.mxp1.MXParser.parseProlog(MXParser.java:1447)
>   at org.xmlpull.mxp1.MXParser.nextImpl(MXParser.java:1395)
>   at org.xmlpull.mxp1.MXParser.next(MXParser.java:1093)
>   at 
> com.thoughtworks.xstream.io.xml.XppReader.pullNextEvent(XppReader.java:109)
> Caused: com.thoughtworks.xstream.io.StreamException:  : only 1.0 is supported 
> as  version=\'1.1\'... @1:19) 
>   at 
> com.thoughtworks.xstream.io.xml.XppReader.pullNextEvent(XppReader.java:124)
>   at 
> com.thoughtworks.xstream.io.xml.AbstractPullReader.readRealEvent(AbstractPullReader.java:148)
>   at 
> com.thoughtworks.xstream.io.xml.AbstractPullReader.readEvent(AbstractPullReader.java:141)
>   at 
> com.thoughtworks.xstream.io.xml.AbstractPullReader.move(AbstractPullReader.java:118)
>   at 
> com.thoughtworks.xstream.io.xml.AbstractPullReader.moveDown(AbstractPullReader.java:103)
>   at com.thoughtworks.xstream.io.xml.XppReader.(XppReader.java:63)
>   at 
> com.thoughtworks.xstream.io.xml.AbstractXppDriver.createReader(AbstractXppDriver.java:54)
>   at 
> com.thoughtworks.xstream.io.xml.AbstractXppDriver.createReader(AbstractXppDriver.java:65)
>   at hudson.XmlFile.unmarshal(XmlFile.java:159)
> Caused: java.io.IOException: Unable to read C:\Users\poo\.jenkins\config.xml
>   at hudson.XmlFile.unmarshal(XmlFile.java:161)
>   at jenkins.model.Jenkins.loadConfig(Jenkins.java:3022)
>   at jenkins.model.Jenkins.access$1200(Jenkins.java:304)
>   at jenkins.model.Jenkins$16.run(Jenkins.java:3040)
>   at 
> org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)
>   at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)
>   at jenkins.model.Jenkins$7.runTask(Jenkins.java:1064)
>   at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)
>   at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
>   at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown 
> Source)
>   at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown 
> Source)
>   at java.base/java.lang.Thread.run(Unknown Source)
> Caused: org.jvnet.hudson.reactor.ReactorException
>   at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:269)
>   at jenkins.InitReactorRunner.run(InitReactorRunner.java:47)
>   at jenkins.model.Jenkins.executeReactor(Jenkins.java:1088)
>   at jenkins.model.Jenkins.(Jenkins.java:904)
>   at hudson.model.Hudson.(Hudson.java:85)
>   at hudson.model.Hudson.(Hudson.java:81)
>   at hudson.WebAppMain$3.run(WebAppMain.java:231)
> Caused: hudson.util.HudsonFailedToLoad
>   at hudson.WebAppMain$3.run(WebAppMain.java:248)
>
>
> Regards,
> Poovaraj
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/4c644b8e-6ad5-4913-8269-78e42bdf5afa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.