Re: Pipeline Changes Page

[Quang Truong]

I think I found the issue, don't know how to delete this thread so I update 
the root cause for anyone might encounter the same issue.

We use the checkout step in a shared lib with a hardcode of repository 
browser object to the old repo server

checkout(changelog: true, poll: true,
scm: [$class: 'GitSCM', branches: [[name: '*/' + branchName]],
browser: [$class: 'GitLab',
repoUrl: "/$repoDirName",
version: '8.6'],
doGenerateSubmoduleConfigurations: false,
extensions: extensions,
submoduleCfg: [],
userRemoteConfigs: [[url: repoName]]
])

Hope this can help!




-- 
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/d98d74a4-0028-45dc-8966-dd5f9579e0a9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Pipeline Changes Page

[Quang Truong]

Hi,

I have a problem on the multibranch pipeline when I change the Git 
repository server in the configuration and Jenkinsfile script, everything 
is fine except the Changes page points to the old repository server for all 
the links.

I have updated all configurations in job and system configuration to the 
new repository server but seems there is a hidden place that point to the 
old one.

I can't find many documents about this Changes page and how to have the 
data generated. Got a comment:

"Jenkins keeps local workspace for each job. After the first checkout, that 
workspace will be at certain SCM revision. Next time the job runs, it will 
compare local workspace revision to latest revision on server, and get a 
changelog that way"

But I can't figure out where the local workspace is located, because we use 
the build slave and cleanup the workspace on new build so this must be on 
the master

I found in the build.xml (in 
jobs//branches//builds/



2


git@:.git




*/master


false

http:///
8.6



Please help to give a hint.

PS: I found another note in Git plugin about the Repository Browser which 
set the links in Changes page but I don't see it in any of my job 
configuration. I'm using Jenkins 2.164.3 LTS and Git plugin 3.10.0

Thanks,
Quang



-- 
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/06c02733-43fb-4b46-be5f-d0765256773f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Can't add SonarQube User Token to Jenkins configuration...

[Quang Truong]

Hi Jeff,

You can create the credential with "Secret text" type, which you use the 
token from Sonar as the secret text

Best Regards,
Quang

-- 
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/50886038-fe40-447d-b5b3-6d5f313c4a24%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Unable to create user for JENKINS

[Mahesh Desai]

On trying to create user its displaying SPAM issue.

-- 
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/f37d544d-6a04-4e3f-b1d4-72d66b8c639b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Kubernetes plugin credentials for Google Kubernetes Engine cluster

[Carlos Sanchez]

you can create certificate credentials too, but the best way is to use a
service account token (secret string)

On Tue, Jun 18, 2019 at 11:51 PM samt88  wrote:

> 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.
>

-- 
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/CALHFn6Ph5sQd2sCO5GY9Ks-XpK%3D4FhtnzMC%3Dr35O1f14rFC9eA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Jeremy Hartley]

Hi Ulrich,

Thanks for your suggestion. I'll definitely cross post it to the Developers 
List.

In terms of your question about the UX overhaul. What you suggest makes a 
lot of sense. We are planning to start with a few small changes to improve 
the First TIme Wizard experience and then make some limited (mostly 
CSS-based) improvements to the the Jenkins UX while we gradually plan the 
larger UX overhaul. Our goal is to learn from Blue Ocean and not be in a 
position where we find that though good for Pipelines it is difficult to 
extend out to cover/replace the rest of the UX.

If you have any more comments or follow up I would be really happy to hear.

Thanks

Jeremy Hartley

On Tuesday, June 18, 2019 at 12:02:56 PM UTC+2, Ullrich Hafner wrote:
>
>
> 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 jenkins...@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/416d7df6-2027-41d9-acd9-d46be75c5271%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.