5 ms·

I am the leader of the Blue Ocean project - feel free to ask me anything :) This is just the first release of what we hope to be many more in the coming weeks

by i386 10y ago

I am the leader of the Blue Ocean project - feel free to ask me anything :) This is just the first release of what we hope to be many more in the coming weeks and months. The surface area of Jenkins is _huge_ and we may not have all your use-cases covered - please send us your feedback and feature requests by signing up to https://issues.jenkins-ci.org https://issues.jenkins-ci.org and submit a new issue under the 'blueocean-plugin' component. A few things that are coming up soon: - Support for Github Enterprise - Full read/write from the Visual Pipeline Editor for any Git repository (Github is supported today!) - Visual Pipeline Editor feature parity with Declarative Pipeline

crymer11 10y ago
How can we have multiple Jenkinsfiles in a single branch? We want to run one job to build things, then after we deploy, we want to trigger another job that runs a bunch of integration, performance, etc. tests against the new code.
- hrmpw 10y ago
  Why do you need them to be separate Pipelines? Because it is convenient or for other reasons? Do you want everyone of these jobs in every branch that you create? In Pull Requests? Do you want all of these jobs to automatically trigger on every push the repo? It's possible to do all of these steps in a single Pipeline but I'm curious why you would want to separate it?
  - crymer11 10y ago
    We want to run our integration tests, etc. against our per-branch staging environment and then against prod when we deploy the branch there as well. With a "post-deploy" pipeline file, we can keep that logic nice and clean and easily trigger the appropriate job via the API. With everything in one file, we would have to add the logic to our Jenkins pipeline to handle when to trigger deployments (which is currently done through a service we built that looks at GitHub commit statuses of a certain prefix/listens to Slack slash commands).
- bryanlarsen 10y ago
  We have a massive Jenkinsfile with a whole bunch of when clauses so that it can be run in separate cases. Might be nicer as multiple Jenkinsfile's, but it works.
- relics443 10y ago
  I believe there's a "load" command which takes a path to a jenkinsfile
- jsmeaton 10y ago
  I was dealing with this just yesterday funny enough. We didn't really like the idea of using `load()` to bring in a new file. I'll prefix the rest by saying we haven't actually implemented this yet, so YMMV. Our goal was to have a separate deploy pipeline that wasn't dependent on the test step (for various reasons I won't go into). We decided on creating a new job of type pipeline, and pointing it at a script named `Jenkinsfile.deploy`. It has a few parameters, namely `BRANCH`, that can be manually set, or passed in from another job. We can then move our deployment steps from the main Jenkinsfile into this new one, and still version control the lot. Major caveat is that the deploy step is not compatible with organisation scans (multibranch/pr), but that's fine for our use case. We usually want to trigger our builds manually based on the branch.
  - hrmpw 10y ago
    I was playing around with a combination of Pipeline and Job-DSL and created this as a POC: https://gist.github.com/HRMPW/9b2a3ccbdc370e0a7c9cb541be229da9 https://gist.github.com/HRMPW/9b2a3ccbdc370e0a7c9cb541be229d... This is a Job-DSL seed job written in Declarative Pipeline that pulls in your Organization based on a build parameter and creates two jobs for every repo: 1. A multibranch Pipeline job that is based on the Jenkinsfile that will work across all branches and PRs. 2. A deploy job for the repo that is defined in a "jenkinsfile.deploy" file in the repo. This isn't a multibranch job but can be run on any branch based on a parameter for the branch. This is a very simplistic implementation but could be expanded on further.
  - Chico75 10y ago
    Sounds like you would be better off putting the logic in separate function of a global library that you can then call in different stages for different conditions: https://jenkins.io/doc/book/pipeline/shared-libraries/ https://jenkins.io/doc/book/pipeline/shared-libraries/
    - jsmeaton 10y ago
      For some things, yes, and we are planning to do this. Deployment is different between our projects though, so we'd prefer our deployment method to live within the repo beside other build steps.
- i386 10y ago
  Its possible to include and exclude different stages of the build with any criteria you like using the `when` block. Referring to this example https://gist.github.com/i386/5bacc640574c6d79bb72cd9a1181a505 https://gist.github.com/i386/5bacc640574c6d79bb72cd9a1181a50... if I have a branch called 'feature/cool-feature' then only the stages Build and Test would be run. If the branch is called 'master', all stages in the Pipeline would be run. 'when' also supports environment variables and expressions and even multiple `when` blocks - see the docs at https://jenkins.io/doc/book/pipeline/syntax/#when https://jenkins.io/doc/book/pipeline/syntax/#when
scrollaway 10y ago
Hi James, good to see Blue Ocean entering GA :) It has improved a lot since I last tried it. Although my team is moving towards Travis for everything except server deployments. Pains me to say since I especially appreciate self-hosting, but Jenkins is still massively behind in everything outside of Blue Ocean. :/ For lots of things that are now basic in all CI/CD systems (email/slack/irc notifications, github login, etc), Jenkins still requires external plugins and/or a ton of setup from the really clunky UI. It's too much :( What's the plan to resolve this? Is blue ocean going to spread to the other areas of Jenkins?
- i386 10y ago
  Yes, this is absolutely within our mission to resolve. We've been discussing adding "high level notifications" in declarative and the editor. You can follow along at https://issues.jenkins-ci.org/browse/JENKINS-41687 https://issues.jenkins-ci.org/browse/JENKINS-41687. One thing to note about Blue Ocean is that as we bring in features (For example, better slack and HipChat notifications) we will be making the required plugins dependencies of Blue Ocean. We don't want you to have to think about plugins unless you are going outside our curated experience.
- tokenizerrr 10y ago
  The point of Jenkins is the powerful plugin ecosystem. Installing a few plugins is IMO exactly how it's supposed to be and not at all a burden.
  - piva00 10y ago
    The problem we are facing at my company is: we have a federated Jenkins setup where each team got their own instance and my team managing Jenkins updates, etc. You don't know the pain we suffer from this plugin ecosystem. Installing a bunch of plugins which depends on a bunch of other stuff, there's no real dependency management for this and it's thoroughly painful when one of the teams decide to upgrade one of their plugins and break their whole setup because of it. It has happened before even with basic plugins like "Git", one upgrade completely broke more than 50% of our instances (we are running about 50 instances right now) because a lot of other plugins relied on it and then needed to be upgraded, these upgrades then broke other plugins which depended on them and this started a domino effect. Also, some plugins are just released and never taken care of, we have to maintain about 10 forks of plugins because there's no curation about them. We came to the point where Jenkins flexibility by itself is a liability. I know that Jenkins is wonderful for smaller teams but there's a point where the lack of governance really hurts and it's the main burden about it. But of course, that's a given for any flexibility, too much of it and you have to design boundaries to contain problems... I'm just ranting because after this stint I'm burned about Jenkins, to the point where I don't want ever in my life to have to work with or use it.
jsmeaton 10y ago
Awesome work! We've been migrating to Jenkins v2 and blue ocean over the last couple of weeks. The new experience is way way better. Does the 1.0 release offer much that wasn't in the previous version? Edit: Answering my own question. No, the 1.0rc4 -> 1.0 is just a version bump.
- i386 10y ago
  Thanks for the support and great to hear that you are taking the time to upgrade! We've shipping a lot of bug fixes in the last few releases and the integration of the editor into the Pipeline creation process when you choose Github, which landed in rc1. I recommend upgrading your Blue Ocean ASAP :)
- i386 10y ago
  Yes, rc4 is the same bits as 1.0.0
gtirloni 10y ago
Congratulations on the new release! Jenkins: 2.46.1 Blue Ocean: 1.0.0 I click on "New Pipeline", enter the GitHub token, select organization, select repository (without Jenkinsfile in it) and then after a while this message shows up: -- Pipeline Creation Pending... Pipelines are still waiting to be created. You may now return to the Dashboard to check for new pipelines. -- I don't see any errors in the log file or in the browser console. Any insights? EDIT: In the traditional UI, I see a new job was created for my GitHub organization but it has no repositories (probably due to missing Jenkinsfile?) I had to click the "Show more" button on Blue Ocean 10x until I reached the end of my job list (when I was looking for this new pipeline that would have been created).
- i386 10y ago
  Hmm thats no good - would you be able to email me [1] your server log? Usually this happens when the network is slow but something else might be up. If you delete the multibranch project and try again, does it work the second time? It would be good if you could capture a HAR file [2] of your browser session too. [1] jdumay@cloudbees.com [2] https://support.cloudbees.com/hc/en-us/articles/204498690-Diagnosing-Pages-which-Won-t-Render-Correctly https://support.cloudbees.com/hc/en-us/articles/204498690-Di...
  - gtirloni 10y ago
    Just did, thank you! Deleting it and following the "New Pipeline" flow again has the same result.
Yuioup 10y ago
React, Angular or vue?
- fuckemem 10y ago
  or Knockout?
- i386 10y ago
  React
i386 10y ago
If you are a frontend developer who loves developer tools, has worked with SPAs and React - we've got an opening on the Blue Ocean team at CloudBees https://t.co/6ZP1faehVq https://t.co/6ZP1faehVq
alimbada 10y ago
There's a glaring UX issue with Blue Ocean which I'm surprised hasn't been addressed yet: whilst a build is running, the console output forces the page to always scroll to the bottom and it's extremely difficult to stop it from doing this; I end up hitting Home a bunch of times and trying to collapse the console output. It usually takes at least 5 tries to align my mouse cursor with the collapse button before I manage to hit it. Please fix this ASAP. There are other minor issues I've come across, but since this one is extremely annoying I thought I'd mention it here.
- i386 10y ago
  This is a known issue and is slated to land in our 1.1 very shortly You can watch this ticket for updates https://issues.jenkins-ci.org/browse/JENKINS-38523 https://issues.jenkins-ci.org/browse/JENKINS-38523
  - alimbada 10y ago
    Good to hear. Thanks!
eVeechu7 10y ago
Can a Jenkinsfile completely obsolete the config.xml that each job has? Clicking through the gui to create jobs is error-prone, so I'm using jenkins job builder at the moment to create those, but it would be great to just use the one file in tree.
- Chico75 10y ago
  Yes, this is what we are using at our my company. Each team is responsible for their own Jenkins job by writing their own Jenkinsfile (with guidelines and support)
empath75 10y ago
Can you explain how the visual pipeline editor is supposed to work, because the documentation for it is essentially non existent. The version I have installed after upgrading to blue ocean 1 seems to be .2 It doesn't seem to be able to edit pipelines in any way. If I switch to experimental version 1, I get a pipeline editor that basically allows me to view source, but I can't edit any jobs or save a job. Just in general, the documentation for a 1.0 release seems really insufficient.
- kzantow 10y ago
  Sure, we'll make sure to get the docs done in the near future, keep in mind, while Blue Ocean is 1.0 the visual editor isn't quite there yet. There are a few major things we need to get done with the visual editor before it could be called 1.0; the backlog in the Jenkins JIRA has much of the plan laid out, but not all of the design done to see. Right now, the visual editor allows editing _declarative_ pipelines and only allows saving and loading from Github. Support will, of course, be added for the rest of the branch sources but that wasn't ready for the 1.0 Blue Ocean release. In order to use it today, you'll need to set up a Github repository as a branch source and you'll get edit buttons on the branches tab as well as top of the run details.
- i386 10y ago
  We've recorded a short video for how to use the editor https://t.co/NS6LHiRDec https://t.co/NS6LHiRDec
hultner 10y ago
I haven't tested Blue Ocean yet but have used Jenkins previously, I'm currently using your competitor Travis and switched mainly because it's so much easier to get started with for a small project (which usually then grows bigger). From the pictures the new jenkins looks much more pleasant on the eyes but how would you rank it's competitiveness with Travis when it comes to getting started with your testing the first time? Will reconsider Jenkins in my next project as it seems like you are taking UX seriously!
Leynos 10y ago
Are views (https://issues.jenkins-ci.org/browse/JENKINS-39343 https://issues.jenkins-ci.org/browse/JENKINS-39343) coming soon?
- i386 10y ago
  It's on the roadmap but I can't give an ETA at this time.
btd 10y ago
Glad it is GA now, but it is still has some issues: * If i use non core parameter in pipeline, BO ask me to move to classic interface * If i do not use Github like pipeline, interface become partially useless. It means empty branches, empty PR columns etc. Where is good old custom pipelines? But anyway it is good move forward! PS: pipelines itself also has some issues, like really small number of useful steps, literally only sh step used everytime. Also in case of custom pipeline it is still unclear how to abort build in code. And using groovy collections methods is veyr inconvinient (like trying to use .collect to create command like options for next sh step)
- vorg 10y ago
  > using groovy collections methods is veyr inconvinient It looks like Blue Ocean generates Apache Groovy DSL code for the pipeline. From their pipeline doco [1]: _In order to provide durability, which means that running Pipelines can survive a restart of the Jenkins master, Scripted Pipeline must serialize data back to the master. Due to this design requirement, some Groovy idioms such as collection.each { item -> /* perform operation */ } are not fully supported_ I wonder how feasible it is to make any edits at all to the DSL and have the new code read in successfully by the Blue Ocean UX. Perhaps the collections methods aren't the only restrictions. [1] https://jenkins.io/doc/book/pipeline/syntax/#differences-from-plain-groovy https://jenkins.io/doc/book/pipeline/syntax/#differences-fro...
dfinninger 10y ago
Hi! I looked around trying to find a roadmap, and it was a bit difficult (didn't find it). Do you plan on supporting Bitbucket Server like you are with Github Enterprise?
- i386 10y ago
  We are going to publish a public roadmap soon. Yes, we do plan on supporting Bitbucket Cloud and Server but I can't give an ETA on that right now.

by i386 10y ago

crymer11 10y ago

How can we have multiple Jenkinsfiles in a single branch? We want to run one job to build things, then after we deploy, we want to trigger another job that runs a bunch of integration, performance, etc. tests against the new code.

hrmpw 10y ago
Why do you need them to be separate Pipelines? Because it is convenient or for other reasons? Do you want everyone of these jobs in every branch that you create? In Pull Requests? Do you want all of these jobs to automatically trigger on every push the repo? It's possible to do all of these steps in a single Pipeline but I'm curious why you would want to separate it?
- crymer11 10y ago
  We want to run our integration tests, etc. against our per-branch staging environment and then against prod when we deploy the branch there as well. With a "post-deploy" pipeline file, we can keep that logic nice and clean and easily trigger the appropriate job via the API. With everything in one file, we would have to add the logic to our Jenkins pipeline to handle when to trigger deployments (which is currently done through a service we built that looks at GitHub commit statuses of a certain prefix/listens to Slack slash commands).
bryanlarsen 10y ago
We have a massive Jenkinsfile with a whole bunch of when clauses so that it can be run in separate cases. Might be nicer as multiple Jenkinsfile's, but it works.
relics443 10y ago
I believe there's a "load" command which takes a path to a jenkinsfile
jsmeaton 10y ago
I was dealing with this just yesterday funny enough. We didn't really like the idea of using `load()` to bring in a new file. I'll prefix the rest by saying we haven't actually implemented this yet, so YMMV. Our goal was to have a separate deploy pipeline that wasn't dependent on the test step (for various reasons I won't go into). We decided on creating a new job of type pipeline, and pointing it at a script named `Jenkinsfile.deploy`. It has a few parameters, namely `BRANCH`, that can be manually set, or passed in from another job. We can then move our deployment steps from the main Jenkinsfile into this new one, and still version control the lot. Major caveat is that the deploy step is not compatible with organisation scans (multibranch/pr), but that's fine for our use case. We usually want to trigger our builds manually based on the branch.
- hrmpw 10y ago
  I was playing around with a combination of Pipeline and Job-DSL and created this as a POC: https://gist.github.com/HRMPW/9b2a3ccbdc370e0a7c9cb541be229da9 https://gist.github.com/HRMPW/9b2a3ccbdc370e0a7c9cb541be229d... This is a Job-DSL seed job written in Declarative Pipeline that pulls in your Organization based on a build parameter and creates two jobs for every repo: 1. A multibranch Pipeline job that is based on the Jenkinsfile that will work across all branches and PRs. 2. A deploy job for the repo that is defined in a "jenkinsfile.deploy" file in the repo. This isn't a multibranch job but can be run on any branch based on a parameter for the branch. This is a very simplistic implementation but could be expanded on further.
- Chico75 10y ago
  Sounds like you would be better off putting the logic in separate function of a global library that you can then call in different stages for different conditions: https://jenkins.io/doc/book/pipeline/shared-libraries/ https://jenkins.io/doc/book/pipeline/shared-libraries/
  - jsmeaton 10y ago
    For some things, yes, and we are planning to do this. Deployment is different between our projects though, so we'd prefer our deployment method to live within the repo beside other build steps.
i386 10y ago
Its possible to include and exclude different stages of the build with any criteria you like using the `when` block. Referring to this example https://gist.github.com/i386/5bacc640574c6d79bb72cd9a1181a505 https://gist.github.com/i386/5bacc640574c6d79bb72cd9a1181a50... if I have a branch called 'feature/cool-feature' then only the stages Build and Test would be run. If the branch is called 'master', all stages in the Pipeline would be run. 'when' also supports environment variables and expressions and even multiple `when` blocks - see the docs at https://jenkins.io/doc/book/pipeline/syntax/#when https://jenkins.io/doc/book/pipeline/syntax/#when

scrollaway 10y ago

Hi James, good to see Blue Ocean entering GA :) It has improved a lot since I last tried it. Although my team is moving towards Travis for everything except server deployments. Pains me to say since I especially appreciate self-hosting, but Jenkins is still massively behind in everything outside of Blue Ocean. :/ For lots of things that are now basic in all CI/CD systems (email/slack/irc notifications, github login, etc), Jenkins still requires external plugins and/or a ton of setup from the really clunky UI. It's too much :( What's the plan to resolve this? Is blue ocean going to spread to the other areas of Jenkins?

i386 10y ago
Yes, this is absolutely within our mission to resolve. We've been discussing adding "high level notifications" in declarative and the editor. You can follow along at https://issues.jenkins-ci.org/browse/JENKINS-41687 https://issues.jenkins-ci.org/browse/JENKINS-41687. One thing to note about Blue Ocean is that as we bring in features (For example, better slack and HipChat notifications) we will be making the required plugins dependencies of Blue Ocean. We don't want you to have to think about plugins unless you are going outside our curated experience.
tokenizerrr 10y ago
The point of Jenkins is the powerful plugin ecosystem. Installing a few plugins is IMO exactly how it's supposed to be and not at all a burden.
- piva00 10y ago
  The problem we are facing at my company is: we have a federated Jenkins setup where each team got their own instance and my team managing Jenkins updates, etc. You don't know the pain we suffer from this plugin ecosystem. Installing a bunch of plugins which depends on a bunch of other stuff, there's no real dependency management for this and it's thoroughly painful when one of the teams decide to upgrade one of their plugins and break their whole setup because of it. It has happened before even with basic plugins like "Git", one upgrade completely broke more than 50% of our instances (we are running about 50 instances right now) because a lot of other plugins relied on it and then needed to be upgraded, these upgrades then broke other plugins which depended on them and this started a domino effect. Also, some plugins are just released and never taken care of, we have to maintain about 10 forks of plugins because there's no curation about them. We came to the point where Jenkins flexibility by itself is a liability. I know that Jenkins is wonderful for smaller teams but there's a point where the lack of governance really hurts and it's the main burden about it. But of course, that's a given for any flexibility, too much of it and you have to design boundaries to contain problems... I'm just ranting because after this stint I'm burned about Jenkins, to the point where I don't want ever in my life to have to work with or use it.

jsmeaton 10y ago

Awesome work! We've been migrating to Jenkins v2 and blue ocean over the last couple of weeks. The new experience is way way better. Does the 1.0 release offer much that wasn't in the previous version? Edit: Answering my own question. No, the 1.0rc4 -> 1.0 is just a version bump.

i386 10y ago
Thanks for the support and great to hear that you are taking the time to upgrade! We've shipping a lot of bug fixes in the last few releases and the integration of the editor into the Pipeline creation process when you choose Github, which landed in rc1. I recommend upgrading your Blue Ocean ASAP :)
i386 10y ago
Yes, rc4 is the same bits as 1.0.0

gtirloni 10y ago

Congratulations on the new release! Jenkins: 2.46.1 Blue Ocean: 1.0.0 I click on "New Pipeline", enter the GitHub token, select organization, select repository (without Jenkinsfile in it) and then after a while this message shows up: -- Pipeline Creation Pending... Pipelines are still waiting to be created. You may now return to the Dashboard to check for new pipelines. -- I don't see any errors in the log file or in the browser console. Any insights? EDIT: In the traditional UI, I see a new job was created for my GitHub organization but it has no repositories (probably due to missing Jenkinsfile?) I had to click the "Show more" button on Blue Ocean 10x until I reached the end of my job list (when I was looking for this new pipeline that would have been created).

i386 10y ago
Hmm thats no good - would you be able to email me [1] your server log? Usually this happens when the network is slow but something else might be up. If you delete the multibranch project and try again, does it work the second time? It would be good if you could capture a HAR file [2] of your browser session too. [1] jdumay@cloudbees.com [2] https://support.cloudbees.com/hc/en-us/articles/204498690-Diagnosing-Pages-which-Won-t-Render-Correctly https://support.cloudbees.com/hc/en-us/articles/204498690-Di...
- gtirloni 10y ago
  Just did, thank you! Deleting it and following the "New Pipeline" flow again has the same result.

Yuioup 10y ago

React, Angular or vue?

fuckemem 10y ago
or Knockout?
i386 10y ago
React

i386 10y ago

If you are a frontend developer who loves developer tools, has worked with SPAs and React - we've got an opening on the Blue Ocean team at CloudBees https://t.co/6ZP1faehVq https://t.co/6ZP1faehVq

alimbada 10y ago

There's a glaring UX issue with Blue Ocean which I'm surprised hasn't been addressed yet: whilst a build is running, the console output forces the page to always scroll to the bottom and it's extremely difficult to stop it from doing this; I end up hitting Home a bunch of times and trying to collapse the console output. It usually takes at least 5 tries to align my mouse cursor with the collapse button before I manage to hit it. Please fix this ASAP. There are other minor issues I've come across, but since this one is extremely annoying I thought I'd mention it here.

i386 10y ago
This is a known issue and is slated to land in our 1.1 very shortly You can watch this ticket for updates https://issues.jenkins-ci.org/browse/JENKINS-38523 https://issues.jenkins-ci.org/browse/JENKINS-38523
- alimbada 10y ago
  Good to hear. Thanks!

eVeechu7 10y ago

Can a Jenkinsfile completely obsolete the config.xml that each job has? Clicking through the gui to create jobs is error-prone, so I'm using jenkins job builder at the moment to create those, but it would be great to just use the one file in tree.

Chico75 10y ago
Yes, this is what we are using at our my company. Each team is responsible for their own Jenkins job by writing their own Jenkinsfile (with guidelines and support)

empath75 10y ago

Can you explain how the visual pipeline editor is supposed to work, because the documentation for it is essentially non existent. The version I have installed after upgrading to blue ocean 1 seems to be .2 It doesn't seem to be able to edit pipelines in any way. If I switch to experimental version 1, I get a pipeline editor that basically allows me to view source, but I can't edit any jobs or save a job. Just in general, the documentation for a 1.0 release seems really insufficient.

kzantow 10y ago
Sure, we'll make sure to get the docs done in the near future, keep in mind, while Blue Ocean is 1.0 the visual editor isn't quite there yet. There are a few major things we need to get done with the visual editor before it could be called 1.0; the backlog in the Jenkins JIRA has much of the plan laid out, but not all of the design done to see. Right now, the visual editor allows editing _declarative_ pipelines and only allows saving and loading from Github. Support will, of course, be added for the rest of the branch sources but that wasn't ready for the 1.0 Blue Ocean release. In order to use it today, you'll need to set up a Github repository as a branch source and you'll get edit buttons on the branches tab as well as top of the run details.
i386 10y ago
We've recorded a short video for how to use the editor https://t.co/NS6LHiRDec https://t.co/NS6LHiRDec

hultner 10y ago

I haven't tested Blue Ocean yet but have used Jenkins previously, I'm currently using your competitor Travis and switched mainly because it's so much easier to get started with for a small project (which usually then grows bigger). From the pictures the new jenkins looks much more pleasant on the eyes but how would you rank it's competitiveness with Travis when it comes to getting started with your testing the first time? Will reconsider Jenkins in my next project as it seems like you are taking UX seriously!

Leynos 10y ago

Are views (https://issues.jenkins-ci.org/browse/JENKINS-39343 https://issues.jenkins-ci.org/browse/JENKINS-39343) coming soon?

i386 10y ago
It's on the roadmap but I can't give an ETA at this time.

btd 10y ago

Glad it is GA now, but it is still has some issues: * If i use non core parameter in pipeline, BO ask me to move to classic interface * If i do not use Github like pipeline, interface become partially useless. It means empty branches, empty PR columns etc. Where is good old custom pipelines? But anyway it is good move forward! PS: pipelines itself also has some issues, like really small number of useful steps, literally only sh step used everytime. Also in case of custom pipeline it is still unclear how to abort build in code. And using groovy collections methods is veyr inconvinient (like trying to use .collect to create command like options for next sh step)

vorg 10y ago
> using groovy collections methods is veyr inconvinient It looks like Blue Ocean generates Apache Groovy DSL code for the pipeline. From their pipeline doco [1]: _In order to provide durability, which means that running Pipelines can survive a restart of the Jenkins master, Scripted Pipeline must serialize data back to the master. Due to this design requirement, some Groovy idioms such as collection.each { item -> /* perform operation */ } are not fully supported_ I wonder how feasible it is to make any edits at all to the DSL and have the new code read in successfully by the Blue Ocean UX. Perhaps the collections methods aren't the only restrictions. [1] https://jenkins.io/doc/book/pipeline/syntax/#differences-from-plain-groovy https://jenkins.io/doc/book/pipeline/syntax/#differences-fro...

dfinninger 10y ago

Hi! I looked around trying to find a roadmap, and it was a bit difficult (didn't find it). Do you plan on supporting Bitbucket Server like you are with Github Enterprise?

i386 10y ago
We are going to publish a public roadmap soon. Yes, we do plan on supporting Bitbucket Cloud and Server but I can't give an ETA on that right now.