Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Oct 04 2018 05:48

    vrutkovs on pyup-update-ansible-2.3.2.0-to-2.6.5

    (compare)

  • Oct 04 2018 05:48
    pyup-bot closed #89
  • Oct 04 2018 05:48
    pyup-bot commented #89
  • Oct 04 2018 05:48
    pyup-bot opened #90
  • Oct 04 2018 05:48

    vrutkovs on pyup-update-ansible-2.3.2.0-to-2.7.0

    Update ansible from 2.3.2.0 to … (compare)

  • Oct 04 2018 05:48

    vrutkovs on pyup-update-ansible-2.3.2.0-to-2.7.0

    (compare)

  • Sep 28 2018 22:33

    vrutkovs on pyup-update-ansible-2.3.2.0-to-2.6.4

    (compare)

  • Sep 28 2018 22:33
    pyup-bot closed #88
  • Sep 28 2018 22:33
    pyup-bot commented #88
  • Sep 28 2018 22:33
    pyup-bot opened #89
  • Sep 28 2018 22:33

    vrutkovs on pyup-update-ansible-2.3.2.0-to-2.6.5

    Update ansible from 2.3.2.0 to … (compare)

  • Sep 28 2018 22:33

    vrutkovs on pyup-update-ansible-2.3.2.0-to-2.6.5

    (compare)

  • Sep 07 2018 00:02

    vrutkovs on pyup-update-ansible-2.3.2.0-to-2.6.3

    (compare)

  • Sep 07 2018 00:02
    pyup-bot closed #87
  • Sep 07 2018 00:02
    pyup-bot commented #87
  • Sep 07 2018 00:02
    pyup-bot opened #88
  • Sep 07 2018 00:02

    vrutkovs on pyup-update-ansible-2.3.2.0-to-2.6.4

    Update ansible from 2.3.2.0 to … (compare)

  • Sep 07 2018 00:02

    vrutkovs on pyup-update-ansible-2.3.2.0-to-2.6.4

    (compare)

  • Aug 17 2018 02:32

    vrutkovs on pyup-update-ansible-2.3.2.0-to-2.6.2

    (compare)

  • Aug 17 2018 02:31
    pyup-bot closed #86
Marek Goldmann
@goldmann
this is how I use it at least
added a makefile to make it easier to release: just make release
Vadim Rutkovsky
@vrutkovs
LGTM, merged
Marek Goldmann
@goldmann
once you merge it, please make sure you immediately re-tag 1.0 and bump the version to "1.1.dev" or whatever the next version will be
this time you'll not overwrite the version accidentally :)
and i just added you as owner to the pypi package
you can now release on your own :)
Vadim Rutkovsky
@vrutkovs
that wasn't easy, but I managed to screw up :)
@goldmann okay, works fine now. Huge thanks!
Marek Goldmann
@goldmann
yw!
the important thing is the correct version in version.py file
(while releasing)
Vadim Rutkovsky
@vrutkovs
yeah, I got used to a similar schema in GNOME, I guess we'll be fine
Vadim Rutkovsky
@vrutkovs
@goldmann long time no see!
Marek Goldmann
@goldmann
aye :)
Vadim Rutkovsky
@vrutkovs
so I'll use the code you've shown to rewrite the steps to docker-py - Containers-Testing-Framework/common-steps#10
that's probably the blocker for 2.0 release, gonna try playing with it this week
Marek Goldmann
@goldmann
makes sense, thanks for all the help
Vadim Rutkovsky
@vrutkovs
I'll probably meet @l-d-j on one of these Prague Docker meetups and discuss the strategy there. Marek, you should come too someday!
Marek Goldmann
@goldmann
yah, we talked about it with David
Vadim Rutkovsky
@vrutkovs
awesome
Since Fedora now has a proper OSBS running we could suggest using CTF for tests
starting with cockpit folks maybe
Marek Goldmann
@goldmann
definitely
vrutkovs: I would need probably talk with you about best practices for tests
Vadim Rutkovsky
@vrutkovs
@goldmann: yeah, good idea. I could show some behave tricks
Marek Goldmann
@goldmann
I have issues with sharing scripts which should be run for different images - but same tests
we use heavily tags, obviously
Vadim Rutkovsky
@vrutkovs
I think the best way to share steps is git submodules
Marek Goldmann
@goldmann
but I think how we could the best referenve these tests in both image repos
oh no
:)
Vadim Rutkovsky
@vrutkovs
the rest is even worse :)
Marek Goldmann
@goldmann
seriously?
geez
Vadim Rutkovsky
@vrutkovs
well, maybe local python packages? But that's not really reliable
Marek Goldmann
@goldmann
the problem with submodules is that we need to commit somewhere a change to a test, then go back, and update our repo
so, 2 commits
ideally I would like to have one
ideally, test would sit next to the image source
Vadim Rutkovsky
@vrutkovs
I think there is a way to make submodules point to a head of the branch, isn't it?
Marek Goldmann
@goldmann
but we cannot use that since we need to be able to rebuild and test at any time
with proper tests which were available at the time of image release
Vadim Rutkovsky
@vrutkovs
hmm, okay, maybe CTF should have its own format to solve that
Marek Goldmann
@goldmann
maybe
this is in fact fairly complicated issue
currently we have every test in one repo and we have submodules
this doesn't work really well :(
Vadim Rutkovsky
@vrutkovs
yeah, I'll discuss that with David
Marek Goldmann
@goldmann
cool