Problem in Pier job
Locked
 
|
In case you didn't notice, the Pier job is broken for a few days now:
https://ci.inria.fr/pharo-contribution/job/Pier3/? It looks related to Grease and there has been a discussion about a similar problem in the "Voyage cannot be load" thread of the Pharo mailing list. I don't know what to do and don't have time to look at it. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill _______________________________________________ Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki |
|
|
On Tue, Mar 25, 2014 at 11:47 AM, Damien Cassou <[hidden email]> wrote:
> > It looks related to Grease and there has been a discussion about a > similar problem in the "Voyage cannot be load" thread of the Pharo > mailing list. I don't know what to do and don't have time to look at > it. if nobody bothers having a look, I think I will just remove my email address from the Jenkins notifications because this is very annoying. And don't tell me I should pay attention to not break Pier when making changes to Pillar. If you don't care, why should I? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill _______________________________________________ Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki |
|
|
Hi, There really is no point anymore in getting stuck with maintaining a development Pier version for Pharo 2. We do not have the manpower for that, and we should focus on the latest version.
Doru On Tue, Apr 1, 2014 at 10:02 AM, Damien Cassou <[hidden email]> wrote:
"Every thing has its own flow"
_______________________________________________ Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki |
|
|
Am 01.04.2014 um 10:35 schrieb Tudor Girba <[hidden email]>: The problem really is the way we use metacello. As long as static versions refer to symbolic versions like #stable the problem will persist. I agree with you that there is no need to maintain a pier for pharo 2. But at the same time it should be possible load old code to build an old pier that works with older versions. Norbert
_______________________________________________ Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki |
|
|
If you look at the build job, you will see that the stable version works for both Pharo 2 and Pharo 3. It's only the development version that has a problem with Pharo 2 and nobody cares (nor should one care) about it. So, we should just remove the development job for Pharo 2. Who could do that? Doru On Tue, Apr 1, 2014 at 10:54 AM, Norbert Hartl <[hidden email]> wrote:
"Every thing has its own flow"
_______________________________________________ Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki |
|
|
2014-04-01 10:26 GMT+01:00 Tudor Girba <[hidden email]>:
Not directly related, but I´ve only been able to get a proper Pier setup with the one-click images from lukas' site, which are built with Pharo 1.3. The builds downloaded from CI have a bunch of issues, like showing the commands even to non-logged users, missing links to the management components, or the file settings component throwing some DNU on a MAFileSomething. I just thought it worth mentioning.
Cheers, Sergi _______________________________________________ Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki |
|
|
Please enter separate issues, describing versions and platform. I have a production deployed Pharo3 Pier. Pharo2 development is waiting for a Seaside version upgrade. No need to delete builds. A need to evaluate CM practices though Stephan Verstuurd vanaf mijn iPhone
_______________________________________________ Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki |
|
|
2014-04-01 13:55 GMT+01:00 Stephan Eggermont <[hidden email]>:
Sure, just point me to the tracker and probably give me a few guidelines so I can make the reports as useful as possible. I´m really interested in deploying Pier3 on Pharo3 for a couple of sites that I have in mind, but seeing those faults scared me a bit, and a short investigation/fixing attempt left me worse than I was :D. Ideally, I´d like to figure out how to fix the possible issues and contribute the fixes back so everyone can enjoy the latest and shiniest Pier running on the the latest and shiniest Pharo.
Cheers, Sergi _______________________________________________ Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki |
|
|
In reply to this post by Damien Cassou
You can describe issues here on the list or on our issue tracker:
https://code.google.com/p/pier/issues/list Pharo contributions CI creates 4 different images. It helps to know if the problem is in one or all four. And having issues as separate mails helps focus. The issues we found with Pier3 on Pharo3 were not difficult to solve. Mostly replacing deprecated and removed functionality (FileSystem, WARenderCanvas) Stephan _______________________________________________ Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki |
«
Return to Magritte, Pier and Related Tools
|
1 view|%1 views
| Free forum by Nabble | Edit this page |