sh '/usr/local/bin/docker-compose -f docker-compose.builder.yml build image'
withCredentials([file(credentialsId: '8da5ba56-8ebb-4a6a-bdb5-43c9d0efb120', variable: 'ENV_FILE')])
SolDevelo Sp. z o.o. [LLC] / www.soldevelo.com
Al. Zwycięstwa 96/98, 81-451, Gdynia, Poland
Phone: +48 58 782 45 40 / Fax: +48 58 782 45 41
--
You received this message because you are subscribed to the Google Groups "OpenLMIS Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openlmis-dev...@googlegroups.com.
To post to this group, send email to openlm...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/2195ef7b-76f2-4dd7-ba37-d0d6c0e400dd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
On 2) - with the number of (breaking) changes to our endpoints in
all our services, I'd be hesitant to just use the latest
ref-distro image versions and assume this will work for with the
built patch images in most cases. Ideally, our API would be more
stable, but I don't think we are there yet. My feeling is that we
would very quickly run into a problem with failing contract test
because there were breaking changes introduced to one or more
services during current development.
Perhaps a simple ability to override this default behavior of
using latest ref-distro versions would be sufficient? I know this
would require to manually click the button to run the job and
specify the versions, but this would provide a working alternative
for automated patch builds that break due to the contract test
failures caused by breaking API changes.
Any thoughts?
Sebastian.
To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/DB88D06F-94A2-44D4-92F7-2D6366B5D556%40villagereach.org.
For more options, visit https://groups.google.com/d/optout.
Sebastian
Brudziński
Senior Software Developer / Team
Leader
sbrud...@soldevelo.com
Hi Josh and Sebastian,
thanks for your feedback!
1) It seems that we don't need to push these images with -build#
suffix. We can just tag the image and use it in sonar analysis and
contract tests. If they pass, we could push the actual tag (e.x.
10.0.0-SNAPSHOT). Is there any case where we would want to publish
"1.0.0-SNAPSHOT-build174"?
To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/71f45415-ff46-e25c-6d22-681504f42cf7%40soldevelo.com.
For more options, visit https://groups.google.com/d/optout.
Jakub Kondrat
Software Developer
jkon...@soldevelo.com