Ok,
bringing back the discussion I just had with Sebastian (has problems accessing
the mailing list at his current customer).
I see the following problems with the current build pipeline:
1. The second "deploy" execution runs the build and tests double
2. The site should be generated on the same
Ok I think I have a valid solution
I left things pretty much the way they were, but excluded most of the plugin
executions that would usually kick in in the deploy step.
Now it seems as only the steps we want are executed. I definitely like this now
as now we are really only deploying things if
All,
My first day of retirement starts tomorrow! At this time it’s unclear what my
level of participation in Edgent and PLC4X will become. We’ll just have to see
how it goes.
I’m encouraged by the synergy between Edgent and PLC4X. Chris is a great
promoter and contributor so I’m optimistic
Hi Chris,
Looks good.
Regarding the problem with the missing graphviz. We could do a stash after the
build and lets the site stages run all on the git-websites node.
What do you think?
Sebastian
> Am 28.02.2018 um 12:00 schrieb Christofer Dutz :
>
> Ok I think I have a valid solution
>
> I
Hi Sebastian,
I think we should simply wait till we have our vm and keep the current build
till that's done.
Even if the stash option seems to work, it does offload the work to the git
system. Shelving the entire workspace doesn't feel right. Don't want to waste
ASF's resources.
Chris
Outloo
