Shipping everything
a project by cschum
Updated over 5 years ago. 7 hacker ♥️.

Writing code is wonderful, but it gets its real value, when it's released and shipped to the world. You know the mantra: "Release early, release often".

Releasing code is not hard, but it involves a lot of details, and you want to get them right, because a release is this public statement "Hey, it's done, it works, you can use it." and you can't take a release back, once it's out there. To help with releases there are tons of release scripts which try to automate things. But they usually are quite fragile in case something goes wrong and a pain to test and maintain.

This Hack Week project is about changing this and solving the problem of release scripts once and for all.

The goal is to write a tool which automates releases for every thinkable project. It goes under the name Yes, Ship It!. There is code. Read more about the technical concept in the README.

You are welcome to contribute. Feedback, bug reports, patches, whatever helps to improve the tool.

I'm particularly interested in releases of your own projects you do during Hack Week. Maybe we can make yes_ship_it work for these. If you are interested in giving this a try, please let me know.

And wouldn't it be great to collect all the software releases we do at Hack Week at a central place? With yes_ship_it we could automate that.

Update: We are shipping! We have shipped the first releases as can be seen on our release tracker. The project is self-hosting now, it can ship itself. The next steps are to make it work for as many other projects as we can. Things to do are tracked on the project's issue tracker.

Join this project

Looking for hackers with the skills:

ruby

This project is part of:

Hack Week 13

Activity

  • almost 2 years ago: oholecek disliked this project.
  • over 6 years ago: dmaiocchi liked this project.
  • about 9 years ago: mvidner liked this project.
  • about 9 years ago: okurz liked this project.
  • about 9 years ago: joeyli liked this project.
  • about 9 years ago: mamorales liked this project.
  • about 9 years ago: mamorales joined this project.
  • about 9 years ago: hennevogel liked this project.
  • about 9 years ago: oholecek liked this project.
  • about 9 years ago: gsanso liked this project.
  • about 9 years ago: cschum added keyword "ruby" to this project.
  • about 9 years ago: cschum started this project.
  • about 9 years ago: cschum originated this project.


    • Comments

    • mamorales
      about 9 years ago by mamorales | Reply

      If you are using Yes, Ship It! you can now register your releases with the Yes, It Shipped service here

    Similar Projects

    Recipes catalog and calculator in Rails 8 by gfilippetti

    My wife needs a website to catalog and sell the products of her upcoming bakery, and I need to learn and practice modern Rails. So I'm using this Hack Week to build a modern store using the latest Ruby on Rails best practices, ideally up to the deployment.

    TO DO

    • Index page
    • Product page
    • Admin area -- Supplies calculator based on orders -- Orders notification
    • Authentication
    • Payment
    • Deployment

    Day 1

    As my Rails knowledge was pretty outdated and I had 0 experience with Turbo (wich I want to use in the app), I started following a turbo-rails course. I completed 5 of 11 chapters.

    Day 2

    Continued the course until chapter 8 and added live updates & an empty state to the app. I should finish the course on day 3 and start my own project with the knowledge from it.

    Hackweek 24

    For this Hackweek I'll continue this project, focusing on a Catalog/Calculator for my wife's recipes so she can use for her Café.

    Day 1

    Fix RSpec tests in order to replace the ruby-ldap rubygem in OBS by enavarro_suse

    Description

    "LDAP mode is not official supported by OBS!". See: config/options.yml.example#L100-L102

    However, there is an RSpec file which tests LDAP mode in OBS. These tests use the ruby-ldap rubygem, mocking the results returned by a LDAP server.

    The ruby-ldap rubygem seems no longer maintaned, and also prevents from updating to a more recent Ruby version. A good alternative is to replace it with the net-ldap rubygem.

    Before replacing the ruby-ldap rubygem, we should modify the tests so the don't mock the responses of a LDAP server. Instead, we should modify the tests and run them against a real LDAP server.

    Goals

    Goals of this project:

    • Modify the RSpec tests and run them against a real LDAP server
    • Replace the net-ldap rubygem with the ruby-ldap rubygem

    Achieving the above mentioned goals will:

    • Permit upgrading OBS from Ruby 3.1 to Ruby 3.2
    • Make a step towards officially supporting LDAP in OBS.

    Resources