I can also add it to the PNNL mega issue thread once it's opened.
________________________________
From: Ben Albrecht <[email protected]>
Sent: Wednesday, July 25, 2018 7:45:50 AM
To: Stavenger, Timothy J; [email protected]
Subject: Re: [Chapel-developers] Chapel master Docker image?
Tim,
> Would it be possible to add a new image that gets updated periodically from
> master?
That's a great idea. I don't think this would be too difficult to set up. Would
you mind opening an issue on chapel-lang/chapel to provide us a mechanism for
prioritizing/assigning this task and discussing the details?
Thanks,
~ben
________________________________
From: Stavenger, Timothy J <[email protected]>
Sent: Wednesday, July 25, 2018 10:16:19 AM
To: [email protected]
Subject: [Chapel-developers] Chapel master Docker image?
We’re developing against features in the 1.18 pre-release found in the master
branch. We had been building on GitlabCI using
https://hub.docker.com/r/chapel/chapel/<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Fr%2Fchapel%2Fchapel%2F&data=02%7C01%7C%7C2f1bef3f88cb4ef4c99a08d5f23d63e2%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636681267832729392&sdata=Ym6irXmimRlBGOBmtHtw1BlaCcVY0p4MDvzHQSSvCSc%3D&reserved=0>,
but since we’ve switched to master the builds are failing.
I could pretty easily make my own Docker image against master, but it would be
nice to have an official one. Would it be possible to add a new image that gets
updated periodically from master?
Thanks!
Tim
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Chapel-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/chapel-developers
