Re: GitHub and Bitbucket branch source UI refactoring

Question inline for a specific plugin, but the question may be general enough to merit discussion. On Tuesday, June 20, 2017 at 7:29:33 AM UTC-6, Stephen Connolly wrote: > > OK! Here we are... testing time! > > These are the plugins that are being covered: (download links should be > live in an

Re: GitHub and Bitbucket branch source UI refactoring

JENKINS-45085 captures the problem I was seeing. The multiple-scms plugin causes a null pointer exception in my multi-branch pipeline job when opening the configure URL of the job. That problem is visible with Jenkins 2.46.3 and 2.60.1. Since my environment does not need or use the

Password reset isn't working

I tried to reset my password but I am not receiving the email and now I can't get in. Can an administrator help me with this problem? -- [image: What's New with Xactly] [image: LinkedIn]

Re: Plugin project action NullPointerException after Jenkins restart

Hello Jesse, thank you again for your tips. I have made an update of the code [1] according to my understanding of your comments. Note that I implemented ` RunAction2` methods on both Action

Re: GitHub and Bitbucket branch source UI refactoring

False alarm, or rather, accurate alarm that has nothing to do with the alpha releases of the plugins. I see an NPE in the console log with the released versions of all plugins, using Jenkins 2.46.3. It is an issue, but not an issue with the alpha releases of the plugins. Mark Waite On

Re: GitHub and Bitbucket branch source UI refactoring

Sorry, fat fingers. I have a multi-branch pipeline job defined to read from https://github.com/MarkEWaite/git-client-plugin using Git with username / password credentials. It works as expected with the alpha versions of the plugins. When I "configure" that job, it shows the project

Re: GitHub and Bitbucket branch source UI refactoring

Mark, can you share details win me via hipchat? On 22 June 2017 at 08:04, Mark Waite wrote: > My docker image that I've upgraded is showing an unexpected behavior in a > GitHub (not git) > > > On Friday, June 16, 2017 at 12:19:24 PM UTC-6, Stephen Connolly wrote: >>

Re: GitHub and Bitbucket branch source UI refactoring

My docker image that I've upgraded is showing an unexpected behavior in a GitHub (not git) On Friday, June 16, 2017 at 12:19:24 PM UTC-6, Stephen Connolly wrote: > > Just a quick status update. > > In final stages of this work now. Bobby is being a superstar and reviewing > my 13k LoC change

Re: [Blue Ocean] Getting 403 when trying to create pipeline

I've tried both. On Tuesday, 20 June 2017 16:52:08 UTC-4, Keith Zantow wrote: > > Did you use the link in the Blue Ocean UI to create your token or did you > create it manually? > > > On Tue, Jun 20, 2017 at 4:14 PM, Th3Alibi > wrote: > >> I am having a hard time using Blue

Re: GitHub and Bitbucket branch source UI refactoring

On Thu, Jun 22, 2017 at 7:19 AM Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > In any case we are probably more interested in other Bitbucket users as at > most you (Mark) would end up using the CloudBees testing Bitbucket Server > instance which is the same one I used and we are

Re: GitHub and Bitbucket branch source UI refactoring

In any case we are probably more interested in other Bitbucket users as at most you (Mark) would end up using the CloudBees testing Bitbucket Server instance which is the same one I used and we are more interested in testing a variety of configurations not multiple people testing the same

Re: GitHub and Bitbucket branch source UI refactoring

It's now known as the BitBucket Branch Source plugin... but the plugin short-name is cloudbees-bitbucket-branch-source On 22 June 2017 at 13:41, Mark Waite wrote: > I used the experimental update center to update to the latest beta plugin > versions. I didn't have

Re: GitHub and Bitbucket branch source UI refactoring

I used the experimental update center to update to the latest beta plugin versions. I didn't have access from my Jenkins to the CloudBees BitBucket Source Branch plugin, so I'm ignoring it. Mark Waite On Thu, Jun 22, 2017 at 4:56 AM Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: >

Re: GitHub and Bitbucket branch source UI refactoring

So yes, it's github-branch-source 2.2.0-alpha-3 that is required for as good as possible inter-op with BlueOcean. Note that when using BlueOcean with GitHub Org Folders you will fall victim to JENKINS-45058 irrespective of the version of GitHub Branch Source that you are using... the migration to

Re: GitHub and Bitbucket branch source UI refactoring

It does look better now with the new version. I confirmed running a scan didn't make anything go away. On Thursday, June 22, 2017 at 3:20:37 PM UTC+10, Stephen Connolly wrote: > > > On Thu 22 Jun 2017 at 04:29, Michael Neale > wrote: > >> I saw all jobs disappear in a

Re: GitHub and Bitbucket branch source UI refactoring

I will try and get around to testing it today. Den onsdag den 21. juni 2017 kl. 20.30.03 UTC+2 skrev Stephen Connolly: > > How many people have been able to try this so far? > > On Tue 20 Jun 2017 at 14:52, Stephen Connolly > wrote: > >> If you are chomping at the bit,

Re: GitHub and Bitbucket branch source UI refactoring

I believe the issue is due to BlueOcean continually replacing the GitHubSCMNavigator and the legacy constructor not populating the discovery traits using the legacy defaults. Great that we caught this now. This does point to an issue for anyone using BlueOcean and configuring traits on a