buildkite-builder 1.0.0.beta.1 → 1.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: c22fb54818a96418e345d04ef7e12a65763af08fe6250175d637d575ba2c583a
-  data.tar.gz: 64c066a9f8c3911a19f07a4c17c757ba345298eee3520054dc87d14ed27fb792
+  metadata.gz: 99dafa9c69892d614803f254d86690b24cdca47b5c8d5e6355abfe29180df5e2
+  data.tar.gz: 35e7a93c70449afa735b1ebde2979ecc63e51c8e549031674258083bcaa273f4
 SHA512:
-  metadata.gz: 9ae6894272a6a796b7e7a4b1cff2cad4022fa3c2219a685de70c4079964907964b7e5abf560b04eacbb8d9e1a6dbe703ed9eb4ed7e796bf4eb04a3c5a942b42b
-  data.tar.gz: 27ed5cd611cdcb50957e40e48dfcc8f31b14001132db37c1edc6119f4c83241329561928703f49d4919be3ffa553617f693b765136730fc4c2d364ab6475f1c6
+  metadata.gz: dd431d4a2db144be98214266408f4b6bbaf76ea354347b559fe78149f6225a1ab372b4aa3fe62b38ed1ce7eaf9204a68e81cd37c629d0698e28eaedcf2c0ff2c
+  data.tar.gz: 4c57e2a787c47c77f68582690530ea232f14516256d54e8fb5ede6a3600fa6b83425fb1a5012a687d4caa9c2f12ee03350ba4227f55646cf169118d829775cd2

data/VERSION

@@ -0,0 +1 @@
+1.0.0

data/bin/buildkite-builder

@@ -1,6 +1,6 @@
 #!/usr/bin/env ruby
 # frozen_string_literal: true
 
-require 'buildkite-builder'
+require_relative File.expand_path('../lib/buildkite-builder', __dir__)
 
 Buildkite::Builder::Commands.run

data/exe/buildkite-builder

@@ -0,0 +1,6 @@
+#!/usr/bin/env ruby
+# frozen_string_literal: true
+
+require 'buildkite-builder'
+
+Buildkite::Builder::Commands.run

data/lib/buildkite/builder.rb

@@ -1,13 +1,10 @@
 # frozen_string_literal: true
 
 require 'bundler'
-require 'logger'
 require 'pathname'
 
 module Buildkite
   module Builder
-    VERSION = '1.0.0.beta.1'
-
     autoload :Commands, File.expand_path('builder/commands', __dir__)
     autoload :Definition, File.expand_path('builder/definition', __dir__)
     autoload :FileResolver, File.expand_path('builder/file_resolver', __dir__)

data/lib/buildkite/builder/commands.rb

@@ -7,6 +7,7 @@ module Buildkite
       COMMANDS = {
         'files' => :Files,
         'preview' => :Preview,
+        'run' => :Run
       }.freeze
 
       autoload :Abstract, File.expand_path('commands/abstract', __dir__)

data/lib/buildkite/builder/commands/run.rb

@@ -0,0 +1,17 @@
+# frozen_string_literal: true
+
+module Buildkite
+  module Builder
+    module Commands
+      class Run < Abstract
+        private
+
+        self.description = 'Builds and uploads the generated pipeline.'
+
+        def run
+          Builder::Runner.run
+        end
+      end
+    end
+  end
+end

data/lib/buildkite/builder/runner.rb

@@ -3,6 +3,7 @@
 require 'bundler'
 require 'pathname'
 require 'tempfile'
+require 'logger'
 
 module Buildkite
   module Builder

data/lib/buildkite/pipelines/helpers/soft_fail.rb

@@ -4,6 +4,23 @@ module Buildkite
   module Pipelines
     module Helpers
       module SoftFail
+        def soft_fail(*value)
+          # soft_fail can be an array of exit_statuses or true
+          # https://buildkite.com/docs/pipelines/command-step#soft-fail-attributes
+
+          if value.first == true
+            current = get('soft_fail')
+
+            if current.is_a?(Array)
+              raise ArgumentError, "Cannot set soft_fail to true when it's already an array.\nsoft_fail: #{current}"
+            else
+              set('soft_fail', true)
+            end
+          else
+            super
+          end
+        end
+
         def soft_fail_on_status(*statuses)
           statuses.each do |status|
             soft_fail(exit_status: status)

metadata

@@ -1,17 +1,18 @@
 --- !ruby/object:Gem::Specification
 name: buildkite-builder
 version: !ruby/object:Gem::Version
-  version: 1.0.0.beta.1
+  version: 1.0.0
 platform: ruby
 authors:
 - Ngan Pham
 - Andrew Lee
 autorequire: 
-bindir: bin
+bindir: exe
 cert_chain: []
-date: 2020-11-19 00:00:00.000000000 Z
+date: 2020-12-01 00:00:00.000000000 Z
 dependencies: []
-description: Write a longer description or delete this line.
+description: Buildkite Builder is a tool that provides projects using Buildkite to
+  have dynamic pipeline functionality.
 email:
 - gusto-opensource-buildkite@gusto.com
 executables:
@@ -19,25 +20,21 @@ executables:
 extensions: []
 extra_rdoc_files: []
 files:
-- ".gitignore"
-- ".rspec"
 - CHANGELOG.md
-- CODE_OF_CONDUCT.md
-- Gemfile
-- Gemfile.lock
 - LICENSE.txt
 - README.md
-- Rakefile
+- VERSION
 - bin/buildkite-builder
 - bin/console
 - bin/setup
-- buildkite-builder.gemspec
+- exe/buildkite-builder
 - lib/buildkite-builder.rb
 - lib/buildkite/builder.rb
 - lib/buildkite/builder/commands.rb
 - lib/buildkite/builder/commands/abstract.rb
 - lib/buildkite/builder/commands/files.rb
 - lib/buildkite/builder/commands/preview.rb
+- lib/buildkite/builder/commands/run.rb
 - lib/buildkite/builder/definition.rb
 - lib/buildkite/builder/file_resolver.rb
 - lib/buildkite/builder/github.rb
@@ -115,12 +112,12 @@ required_ruby_version: !ruby/object:Gem::Requirement
       version: 2.3.0
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
-  - - ">"
+  - - ">="
     - !ruby/object:Gem::Version
-      version: 1.3.1
+      version: '0'
 requirements: []
-rubygems_version: 3.1.4
+rubygems_version: 3.1.2
 signing_key: 
 specification_version: 4
-summary: Write a short summary, because RubyGems requires one.
+summary: A gem for programmatically creating Buildkite pipelines.
 test_files: []

data/.gitignore

@@ -1,11 +0,0 @@
-/.bundle/
-/.yardoc
-/_yardoc/
-/coverage/
-/doc/
-/pkg/
-/spec/reports/
-/tmp/
-
-# rspec failure tracking
-.rspec_status

data/.rspec

@@ -1,3 +0,0 @@
---format progress
---color
---require spec_helper

data/CODE_OF_CONDUCT.md

@@ -1,74 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, gender identity and expression, level of experience,
-nationality, personal appearance, race, religion, or sexual identity and
-orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment
-include:
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-* The use of sexualized language or imagery and unwelcome sexual attention or
-advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic
-  address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Our Responsibilities
-
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
-
-Project maintainers have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at andrew.lee@gusto.com. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at [https://contributor-covenant.org/version/1/4][version]
-
-[homepage]: https://contributor-covenant.org
-[version]: https://contributor-covenant.org/version/1/4/

data/Gemfile

@@ -1,13 +0,0 @@
-source "https://rubygems.org"
-
-gemspec
-
-group :development do
-  gem 'bundler', '~> 2.1'
-  gem 'rake'
-
-  gem 'byebug'
-  gem 'pry-byebug'
-  gem 'rspec'
-  gem 'webmock'
-end

data/Gemfile.lock

@@ -1,56 +0,0 @@
-PATH
-  remote: .
-  specs:
-    buildkite-builder (1.0.0.beta.1)
-
-GEM
-  remote: https://rubygems.org/
-  specs:
-    addressable (2.7.0)
-      public_suffix (>= 2.0.2, < 5.0)
-    byebug (11.1.3)
-    coderay (1.1.3)
-    crack (0.4.4)
-    diff-lcs (1.3)
-    hashdiff (1.0.1)
-    method_source (1.0.0)
-    pry (0.13.1)
-      coderay (~> 1.1)
-      method_source (~> 1.0)
-    pry-byebug (3.9.0)
-      byebug (~> 11.0)
-      pry (~> 0.13.0)
-    public_suffix (4.0.6)
-    rake (13.0.1)
-    rspec (3.9.0)
-      rspec-core (~> 3.9.0)
-      rspec-expectations (~> 3.9.0)
-      rspec-mocks (~> 3.9.0)
-    rspec-core (3.9.0)
-      rspec-support (~> 3.9.0)
-    rspec-expectations (3.9.0)
-      diff-lcs (>= 1.2.0, < 2.0)
-      rspec-support (~> 3.9.0)
-    rspec-mocks (3.9.0)
-      diff-lcs (>= 1.2.0, < 2.0)
-      rspec-support (~> 3.9.0)
-    rspec-support (3.9.0)
-    webmock (3.10.0)
-      addressable (>= 2.3.6)
-      crack (>= 0.3.2)
-      hashdiff (>= 0.4.0, < 2.0.0)
-
-PLATFORMS
-  ruby
-
-DEPENDENCIES
-  buildkite-builder!
-  bundler (~> 2.1)
-  byebug
-  pry-byebug
-  rake
-  rspec
-  webmock
-
-BUNDLED WITH
-   2.1.4

data/Rakefile

@@ -1,6 +0,0 @@
-require "bundler/gem_tasks"
-require "rspec/core/rake_task"
-
-RSpec::Core::RakeTask.new(:spec)
-
-task :default => :spec

data/buildkite-builder.gemspec

@@ -1,28 +0,0 @@
-$LOAD_PATH.unshift File.expand_path('lib', __dir__)
-require 'buildkite-builder'
-
-Gem::Specification.new do |spec|
-  spec.name          = "buildkite-builder"
-  spec.version       = Buildkite::Builder::VERSION
-  spec.authors       = ["Ngan Pham", "Andrew Lee"]
-  spec.email         = ["gusto-opensource-buildkite@gusto.com"]
-
-  spec.summary       = %q{Write a short summary, because RubyGems requires one.}
-  spec.description   = %q{Write a longer description or delete this line.}
-  spec.homepage      = 'https://github.com/Gusto/buildkite-builder'
-  spec.license       = 'MIT'
-  spec.required_ruby_version = Gem::Requirement.new(">= 2.3.0")
-
-  spec.metadata["homepage_uri"] = spec.homepage
-  spec.metadata["source_code_uri"] = "https://github.com/Gusto/buildkite-builder"
-  spec.metadata["changelog_uri"] = "https://github.com/Gusto/buildkite-builder/blob/master/CHANGELOG.md"
-  spec.metadata["bug_tracker_uri"] = "https://github.com/Gusto/buildkite-builder/issues"
-
-  # Specify which files should be added to the gem when it is released.
-  # The `git ls-files -z` loads the files in the RubyGem that have been added into git.
-  spec.files         = Dir.chdir(File.expand_path('..', __FILE__)) do
-    `git ls-files -z`.split("\x0").reject { |f| f.match(%r{^(test|spec|features)/}) }
-  end
-  spec.executables   = ['buildkite-builder']
-  spec.require_paths = ["lib"]
-end