Build Stages

Travis-ci.org currently has nice beta features that I've wanted to try for a [long while(#https://travis-ci.org/foursixnine/openQA/builds/280652163)...

This is to play around a bit with it, and try to improve our build's success rate in openQA.

  • https://docs.travis-ci.com/user/build-stages/
  • https://docs.travis-ci.com/user/conditional-builds-stages-jobs/

Looking for hackers with the skills:

travis yaml

This project is part of:

Hack Week 16

Activity

  • about 7 years ago: szarate started this project.
  • about 7 years ago: szarate liked this project.
  • about 7 years ago: szarate added keyword "travis" to this project.
  • about 7 years ago: szarate added keyword "yaml" to this project.
  • about 7 years ago: szarate originated this project.

  • Comments

    • szarate
      about 7 years ago by szarate | Reply

      They have a nice CLI that proved to be useful for linting the yaml and for triggering and monitoring jobs!

      • travis.ruby2.4 lint .travis.yml
      • git commit -m "test" --amend .travis.yml
      • travis.ruby2.4 show -r foursixnine/openQA

      There's already a Pull request for this: https://github.com/os-autoinst/openQA/pull/1496

    • szarate
      about 7 years ago by szarate | Reply

      https://travis-ci.org/foursixnine/openQA/builds/302644062 ran using a conditional build which was very easy to use :)

    • szarate
      about 7 years ago by szarate | Reply

      Also some feedback was given: https://github.com/travis-ci/beta-features/issues/28#issuecomment-344700330

    Similar Projects

    Create object oriented API for perl's YAML::XS module, with YAML 1.2 Support by tinita

    Description

    YAML::XS is a binding to libyaml and already quite old, but the most popular YAML module for perl. There are two main issues:

    • It uses global package variables to influence behaviour.
    • It didn't implement the loading of types like numbers and booleans according to the YAML spec (neither 1.1 nor 1.2).

    Goals

    Create a new interface which works object oriented. Currently YAML::XS exports a list of functions.

    • The new API will allow to create a YAML::XS object containing configuration influencing the behaviour of loading and dumping.
      • It keeps the libyaml parser and emitter structs in memory, so repeated calls can save the creation of those structs
    • It will by default implement the YAML 1.2 Core Schema, so it is compatible to other YAML processors in perl and in other languages
    • If I have time, I would like to add the merge << key feature as an option. We could then use it in openQA as a replacement for YAML::PP to be faster.

    I already created a proof of concept with a minimal functionality some weeks before this HackWeek.

    Resources