Pipeline is not perfect but definitively is more mature than build-flow has ever been (*)
(*) I'm build-flow initial author, and gave up for major technical limitations 2016-05-24 16:48 GMT+02:00 Stefan Thomasson <[email protected]>: > It is said that jenkins 2.x should be backwards compatible so I not really > sure why buildflow break the gui. For me it only dissapear when navigating > using the tab, so scrolling usually works. > Right now I do not consider pipeline mature enough for use in production > but you may be of other opinion. > > > 24 maj 2016 kl. 16:09 skrev AJ Ferrigno <[email protected]>: > > Hello, > > We have been using the Build Flow plugin for about a year now. We have a > large block of DSL which we mostly needed for parallel execution. > > I have just tried upgrading to Jenkins 2.2, and I am now unable to edit > the DSL in our existing Build Flow job. I open the job, click > configuration, scroll down to where the DSL would be, and the entire DSL > just disappears from view. The only way I can edit the DSL is to navigate > to the config.xml file on the master, change it there, and then reload > configuration from disk. Obviously, this is an inconvenience. > > I have tried making a brand new (blank) Build Flow job and the same issue > happens. Once I paste in my DSL, save it, then return to the configuration > and scroll down, the DSL box disappears. > > Upgrading to Jenkins 2.6 does not fix the issue (in fact, it breaks other > things sadly). Upgrading all my plugins does not fix the issue. > > It looks like this plugin is deprecated in favor of Pipelines and may no > longer be supported. I will need to investigate Pipelines to see how to > move away from our DSL. However, there was a change this month to link it > to Pipelines. Is it possible to get this problem fixed as well? I even > volunteer myself to fixing it, although I am not a Jenkins developer and > wouldn't know where to start debugging this thing. I'm hoping someone else > would understand why something would disappear from the page as a result of > the 2.2 upgrade. Maybe after having it explained, I can make the hopefully > small code change to get it fixed. > > Thanks in advance, > AJ > > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/9c600c2b-9a10-4f1b-87ed-bf6a8bf90dd6%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/9c600c2b-9a10-4f1b-87ed-bf6a8bf90dd6%40googlegroups.com?utm_medium=email&utm_source=footer> > . > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/E7D7FABA-27AA-4C7F-B93C-735C4F293241%40gmail.com > <https://groups.google.com/d/msgid/jenkinsci-users/E7D7FABA-27AA-4C7F-B93C-735C4F293241%40gmail.com?utm_medium=email&utm_source=footer> > . > > 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANMVJzm-VDKN6nrEyujmC53YezQCjRYY%2BcKazR%2Be3fzEkP5%3DHA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
