Thursday, July 20, 2017

How to trigger a pipeline from other pipeline in Buildkite using JSON format.

if you are using Buildkite, you will find how to "trigger" a pipeline from other pipeline in this link.

All of the examples are in yml format and, I don't know why, it is impossible to find examples in JSON format.

After speaking to the Buildkite support, it is possible to "trigger" pipelines from JSON but it is hard to find the steps to follow.  In their support email they wrote a good information to follow:

You should be able to do something like this to trigger a build on the current pipeline:
$ cat my-pipeline.json
{
"steps": [
{ "trigger": "name-of-pipeline", "commit": "HEAD", "branch": "master" }
]
}
$ buildkite-agent pipeline upload my-pipeline.json

The equivalent YAML is:

$ cat my-pipeline.yml
steps:
trigger: "name-of-pipeline"
commit: "HEAD"
branch: "master"
$ buildkite-agent pipeline upload my-pipeline.yml

If you're running the V3 beta version of our agent, you can use environment variables directly within the pipeline so you can use them in your trigger steps. Here's a docs page about it: https://buildkite.com/docs/pipelines/trigger-step. It'd let you write your pipeline.json like this, and have it "just work"

$ cat my-pipeline.json
{
"steps": [
{ "trigger": "name-of-pipeline", "commit": "$BUILDKITE_COMMIT", "branch": "$BUILDKITE_BRANCH" }
]
}
$ buildkite-agent pipeline upload my-pipeline.json

Tuesday, June 27, 2017

Fixed Shodan API in the old TheHarvester

If you are an old-school man, I am sure you have worked with the old theHarverster to make some OSINT (or whatever they call now to extract/search data from different webpages).

Also, theHarvester is available in Kali Linux.

Well, the problem comes from Shodan. They updated their API and it breaks the theHarvester support of Shodan.

I wrote an issue and, finally, spent some minutes to fix it in this PR: https://github.com/laramies/theHarvester/pull/58

I don't know if laramies has deprecated the project.... my contribution is there...

Sunday, June 4, 2017

adsf in homebrew for MacOS

Well, if you don't know asdf, you should.

asdf is an extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more.... i am using it with terraform... super cool and very easy to use it.

They have a good README describing how to install it but they didn't have a brew formula to make it suuuperfast in MacOS.

Well, asdf is available directly in homebrew right now. I wrote a formula for asdf and it was merged:

$ brew info asdf
asdf: stable 0.3.0
Extendable version manager with support for Ruby, Node.js, Erlang & more
https://github.com/asdf-vm
/usr/local/Cellar/asdf/0.3.0 (1,740 files, 275.4MB) *
  Built from source on 2017-06-04 at 09:04:49
From: https://github.com/Homebrew/homebrew-core/blob/master/Formula/asdf.rb
==> Dependencies
Required: autoconf ✔, automake ✘, libtool ✔, coreutils ✔, libyaml ✔, openssl ✔, readline ✔, unixodbc ✔
==> Caveats
Add the following line to your bash profile (e.g. ~/.bashrc, ~/.profile, or ~/.bash_profile)
     source /usr/local/opt/asdf/asdf.sh
Bash completion has been installed to:
  /usr/local/etc/bash_completion.d