VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS0.00%
Net Worth
0.000USD
STEEM
0.001STEEM
SBD
0.000SBD
Effective Power
1.200SP
├── Own SP
0.000SP
└── Incoming DelegationsDeleg
+1.200SP
Detailed Balance
| STEEM | ||
| balance | 0.001STEEM | STEEM |
| market_balance | 0.000STEEM | STEEM |
| savings_balance | 0.000STEEM | STEEM |
| reward_steem_balance | 0.000STEEM | STEEM |
| STEEM POWER | ||
| Own SP | 0.000SP | SP |
| Delegated Out | 0.000SP | SP |
| Delegation In | 1.200SP | SP |
| Effective Power | 1.200SP | SP |
| Reward SP (pending) | 0.000SP | SP |
| SBD | ||
| sbd_balance | 0.000SBD | SBD |
| sbd_conversions | 0.000SBD | SBD |
| sbd_market_balance | 0.000SBD | SBD |
| savings_sbd_balance | 0.000SBD | SBD |
| reward_sbd_balance | 0.000SBD | SBD |
{
"balance": "0.001 STEEM",
"savings_balance": "0.000 STEEM",
"reward_steem_balance": "0.000 STEEM",
"vesting_shares": "0.000000 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "1953.311140 VESTS",
"sbd_balance": "0.000 SBD",
"savings_sbd_balance": "0.000 SBD",
"reward_sbd_balance": "0.000 SBD",
"conversions": []
}Account Info
| name | mojo1jojo2 |
| id | 1324300 |
| rank | 1,502,484 |
| reputation | 60610921 |
| created | 2019-09-30T15:12:15 |
| recovery_account | steem |
| proxy | None |
| post_count | 2 |
| comment_count | 0 |
| lifetime_vote_count | 0 |
| witnesses_voted_for | 0 |
| last_post | 2019-10-08T20:04:03 |
| last_root_post | 2019-10-08T20:04:03 |
| last_vote_time | 1970-01-01T00:00:00 |
| proxied_vsf_votes | 0, 0, 0, 0 |
| can_vote | 1 |
| voting_power | 0 |
| delayed_votes | 0 |
| balance | 0.001 STEEM |
| savings_balance | 0.000 STEEM |
| sbd_balance | 0.000 SBD |
| savings_sbd_balance | 0.000 SBD |
| vesting_shares | 0.000000 VESTS |
| delegated_vesting_shares | 0.000000 VESTS |
| received_vesting_shares | 1953.311140 VESTS |
| reward_vesting_balance | 0.000000 VESTS |
| vesting_balance | 0.000 STEEM |
| vesting_withdraw_rate | 0.000000 VESTS |
| next_vesting_withdrawal | 1969-12-31T23:59:59 |
| withdrawn | 0 |
| to_withdraw | 0 |
| withdraw_routes | 0 |
| savings_withdraw_requests | 0 |
| last_account_recovery | 1970-01-01T00:00:00 |
| reset_account | null |
| last_owner_update | 1970-01-01T00:00:00 |
| last_account_update | 2019-09-30T15:21:24 |
| mined | No |
| sbd_seconds | 0 |
| sbd_last_interest_payment | 1970-01-01T00:00:00 |
| savings_sbd_last_interest_payment | 1970-01-01T00:00:00 |
{
"id": 1324300,
"name": "mojo1jojo2",
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM66bYwKRrHsaBim2jp8yfvsvE62zcUcicNGxcPUz3qymZ2oS7Sw",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM8eReYD1Ai4QYNHqpSxoueAvFLGZ3b7fwTbed2ZmP2rPYXneNqt",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM6k2ZHYuRMkdWT7uyMzgkwJAD82yUxw1tYju59WowpypgebhRJj",
1
]
]
},
"memo_key": "STM82gAZWJND6keUGKH9gMty4hk5d5p6YadYTyvBtv4RhU7LcekkQ",
"json_metadata": "{\"profile\":{\"name\":\"talkabouttech\"}}",
"posting_json_metadata": "",
"proxy": "",
"last_owner_update": "1970-01-01T00:00:00",
"last_account_update": "2019-09-30T15:21:24",
"created": "2019-09-30T15:12:15",
"mined": false,
"recovery_account": "steem",
"last_account_recovery": "1970-01-01T00:00:00",
"reset_account": "null",
"comment_count": 0,
"lifetime_vote_count": 0,
"post_count": 2,
"can_vote": true,
"voting_manabar": {
"current_mana": 1953311140,
"last_update_time": 1588943256
},
"downvote_manabar": {
"current_mana": 488327785,
"last_update_time": 1588943256
},
"voting_power": 0,
"balance": "0.001 STEEM",
"savings_balance": "0.000 STEEM",
"sbd_balance": "0.000 SBD",
"sbd_seconds": "0",
"sbd_seconds_last_update": "1970-01-01T00:00:00",
"sbd_last_interest_payment": "1970-01-01T00:00:00",
"savings_sbd_balance": "0.000 SBD",
"savings_sbd_seconds": "0",
"savings_sbd_seconds_last_update": "1970-01-01T00:00:00",
"savings_sbd_last_interest_payment": "1970-01-01T00:00:00",
"savings_withdraw_requests": 0,
"reward_sbd_balance": "0.000 SBD",
"reward_steem_balance": "0.000 STEEM",
"reward_vesting_balance": "0.000000 VESTS",
"reward_vesting_steem": "0.000 STEEM",
"vesting_shares": "0.000000 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "1953.311140 VESTS",
"vesting_withdraw_rate": "0.000000 VESTS",
"next_vesting_withdrawal": "1969-12-31T23:59:59",
"withdrawn": 0,
"to_withdraw": 0,
"withdraw_routes": 0,
"curation_rewards": 0,
"posting_rewards": 0,
"proxied_vsf_votes": [
0,
0,
0,
0
],
"witnesses_voted_for": 0,
"last_post": "2019-10-08T20:04:03",
"last_root_post": "2019-10-08T20:04:03",
"last_vote_time": "1970-01-01T00:00:00",
"post_bandwidth": 0,
"pending_claimed_accounts": 0,
"vesting_balance": "0.000 STEEM",
"reputation": 60610921,
"transfer_history": [],
"market_history": [],
"post_history": [],
"vote_history": [],
"other_history": [],
"witness_votes": [],
"tags_usage": [],
"guest_bloggers": [],
"rank": 1502484
}Withdraw Routes
| Incoming | Outgoing |
|---|---|
Empty | Empty |
{
"incoming": [],
"outgoing": []
}From Date
To Date
ph-supportsent 0.001 STEEM to @mojo1jojo22022/08/17 07:12:51
ph-supportsent 0.001 STEEM to @mojo1jojo2
2022/08/17 07:12:51
| from | ph-support |
| to | mojo1jojo2 |
| amount | 0.001 STEEM |
| memo | |
| Transaction Info | Block #66875448/Trx 0375c058c02a61766191efa1cca95b63c394eca6 |
View Raw JSON Data
{
"trx_id": "0375c058c02a61766191efa1cca95b63c394eca6",
"block": 66875448,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2022-08-17T07:12:51",
"op": [
"transfer",
{
"from": "ph-support",
"to": "mojo1jojo2",
"amount": "0.001 STEEM",
"memo": ""
}
]
}steemdelegated 1.200 SP to @mojo1jojo22020/05/08 13:07:36
steemdelegated 1.200 SP to @mojo1jojo2
2020/05/08 13:07:36
| delegator | steem |
| delegatee | mojo1jojo2 |
| vesting shares | 1953.311140 VESTS |
| Transaction Info | Block #43197569/Trx efadee39a44bf421f54127dccc621a21f260dc90 |
View Raw JSON Data
{
"trx_id": "efadee39a44bf421f54127dccc621a21f260dc90",
"block": 43197569,
"trx_in_block": 16,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-05-08T13:07:36",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "mojo1jojo2",
"vesting_shares": "1953.311140 VESTS"
}
]
}steemdelegated 6.038 SP to @mojo1jojo22020/01/07 20:27:30
steemdelegated 6.038 SP to @mojo1jojo2
2020/01/07 20:27:30
| delegator | steem |
| delegatee | mojo1jojo2 |
| vesting shares | 9832.639022 VESTS |
| Transaction Info | Block #39729318/Trx 1b5a9a0cab19e58ace365e313fd578a865ac49c7 |
View Raw JSON Data
{
"trx_id": "1b5a9a0cab19e58ace365e313fd578a865ac49c7",
"block": 39729318,
"trx_in_block": 19,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-01-07T20:27:30",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "mojo1jojo2",
"vesting_shares": "9832.639022 VESTS"
}
]
}nin4iupvoted (100.00%) @mojo1jojo2 / benefit-from-multi-repository-dependencies-with-zuul2019/10/08 20:15:27
nin4iupvoted (100.00%) @mojo1jojo2 / benefit-from-multi-repository-dependencies-with-zuul
2019/10/08 20:15:27
| voter | nin4i |
| author | mojo1jojo2 |
| permlink | benefit-from-multi-repository-dependencies-with-zuul |
| weight | 10000 (100.00%) |
| Transaction Info | Block #37113254/Trx 88926adf9bcb3bb78be0b1af1adf23c103cda91b |
View Raw JSON Data
{
"trx_id": "88926adf9bcb3bb78be0b1af1adf23c103cda91b",
"block": 37113254,
"trx_in_block": 22,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-10-08T20:15:27",
"op": [
"vote",
{
"voter": "nin4i",
"author": "mojo1jojo2",
"permlink": "benefit-from-multi-repository-dependencies-with-zuul",
"weight": 10000
}
]
}mojo1jojo2published a new post: benefit-from-multi-repository-dependencies-with-zuul2019/10/08 20:07:09
mojo1jojo2published a new post: benefit-from-multi-repository-dependencies-with-zuul
2019/10/08 20:07:09
| parent author | |
| parent permlink | devops |
| author | mojo1jojo2 |
| permlink | benefit-from-multi-repository-dependencies-with-zuul |
| title | Benefit from Multi Repository Dependencies With Zuul |
| body | @@ -1,8 +1,207 @@ +!%5BMulti Repository Configuration Supported by Zuul.jpg%5D(https://cdn.steemitimages.com/DQmRnFNZepEXyem22k7YhLuFdB4EFZXuPm9cBco8rmLkWVu/Multi%2520Repository%2520Configuration%2520Supported%2520by%2520Zuul.jpg)%0A%0A Ensuring |
| json metadata | {"tags":["continuousintegration","technology","github","git"],"links":["https://vexxhost.com/blog/multi-repository-dependencies-zuul/","https://vexxhost.com/solutions/managed-zuul/"],"app":"steemit/0.1","format":"markdown","image":["https://cdn.steemitimages.com/DQmRnFNZepEXyem22k7YhLuFdB4EFZXuPm9cBco8rmLkWVu/Multi%20Repository%20Configuration%20Supported%20by%20Zuul.jpg"]} |
| Transaction Info | Block #37113088/Trx 27a2726fa0591f2bc068dbe8aff0a37e7bc58bf8 |
View Raw JSON Data
{
"trx_id": "27a2726fa0591f2bc068dbe8aff0a37e7bc58bf8",
"block": 37113088,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-10-08T20:07:09",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "devops",
"author": "mojo1jojo2",
"permlink": "benefit-from-multi-repository-dependencies-with-zuul",
"title": "Benefit from Multi Repository Dependencies With Zuul",
"body": "@@ -1,8 +1,207 @@\n+!%5BMulti Repository Configuration Supported by Zuul.jpg%5D(https://cdn.steemitimages.com/DQmRnFNZepEXyem22k7YhLuFdB4EFZXuPm9cBco8rmLkWVu/Multi%2520Repository%2520Configuration%2520Supported%2520by%2520Zuul.jpg)%0A%0A\n Ensuring\n",
"json_metadata": "{\"tags\":[\"continuousintegration\",\"technology\",\"github\",\"git\"],\"links\":[\"https://vexxhost.com/blog/multi-repository-dependencies-zuul/\",\"https://vexxhost.com/solutions/managed-zuul/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\",\"image\":[\"https://cdn.steemitimages.com/DQmRnFNZepEXyem22k7YhLuFdB4EFZXuPm9cBco8rmLkWVu/Multi%20Repository%20Configuration%20Supported%20by%20Zuul.jpg\"]}"
}
]
}mojo1jojo2published a new post: benefit-from-multi-repository-dependencies-with-zuul2019/10/08 20:04:03
mojo1jojo2published a new post: benefit-from-multi-repository-dependencies-with-zuul
2019/10/08 20:04:03
| parent author | |
| parent permlink | devops |
| author | mojo1jojo2 |
| permlink | benefit-from-multi-repository-dependencies-with-zuul |
| title | Benefit from Multi Repository Dependencies With Zuul |
| body | Ensuring flexibility for developers is essential for an efficient CI/CD tool as it can give significant benefits. Zuul is one such tool that functions on a Git driven philosophy and therefore reads most of its configurations from git repositories. Thus, making limitations a thing of the past through Zuul’s flexible configurations and multi-repository dependencies. Zuul has had an extensive integration with Gerrit, and its latest release, Version 3, supports a much broader range of use cases and development platforms. Some of the most notable being its integration with GitHub. Zuul now supports different development platforms like Git, GitHub, Gerrit, GitHub Enterprise and Pagure. These platforms operate drivers that help Zuul have a configured connection with external systems by implementing the functionality required to connect to them. These drivers can perform any of the following functions: Sources – drivers host git repositories for projects. Zuul can clone these git repositories for projects and download refs. Triggers – drivers emit events; Zuul may respond to these triggers, which are configured in pipelines to cause changes or other refs to be enqueued. Reporters – drivers output information when a pipeline is finished processing an item. Some of the drivers included with Zuul are: GitHub supports all three of the functions mentioned above, sources, triggers and reporters. It can also interact with public GitHub service and site-local installations of GitHub enterprise. Gerrit acts as a code review system and its driver supports sources, triggers and reporters. Pagure, like Github, Pagure drivers support all three of the functions mentioned earlier, sources, triggers and reporters. It can also interact with public Pagure.io service and site-local installations of Pagure. Git can be used to load Zuul’s configurations from public git repositories. It also performs the trigger function to trigger jobs from ref-updated events in a pipeline. Zuul further includes other drivers such as MQTT, SMTP, SQL, Timer and Zuul itself. The first three of these drivers support reporters only whereas the latter two support only triggers. Having multi-repository dependencies comes with benefits for all Zuul users, Multiple repositories make it easy to give access to subsets of repositories on a “need to code” basis. Each repository can have its own process of being deployed, making continuous delivery and deployment easier. Developers take advantage of multiple development platforms to create Adhoc continuous integration tests for exactly what they are working on at the moment. Developers also have the ability to work across project boundaries. Cross community continuous integration testing is also supported via multi-repo. With the option of GitHub Enterprise, all repository data can be stored on your organization’s local network and integrated with your organization’s authentication system. You can read more about it here: https://vexxhost.com/blog/multi-repository-dependencies-zuul/ or check out: https://vexxhost.com/solutions/managed-zuul/ |
| json metadata | {"tags":["devops","continuousintegration","technology","github","git"],"links":["https://vexxhost.com/blog/multi-repository-dependencies-zuul/","https://vexxhost.com/solutions/managed-zuul/"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #37113026/Trx 9e81c2c9abc4572cc58e1709f7c257a8dcfc0d3a |
View Raw JSON Data
{
"trx_id": "9e81c2c9abc4572cc58e1709f7c257a8dcfc0d3a",
"block": 37113026,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-10-08T20:04:03",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "devops",
"author": "mojo1jojo2",
"permlink": "benefit-from-multi-repository-dependencies-with-zuul",
"title": "Benefit from Multi Repository Dependencies With Zuul",
"body": "Ensuring flexibility for developers is essential for an efficient CI/CD tool as it can give significant benefits. Zuul is one such tool that functions on a Git driven philosophy and therefore reads most of its configurations from git repositories. Thus, making limitations a thing of the past through Zuul’s flexible configurations and multi-repository dependencies. Zuul has had an extensive integration with Gerrit, and its latest release, Version 3, supports a much broader range of use cases and development platforms. Some of the most notable being its integration with GitHub.\n\nZuul now supports different development platforms like Git, GitHub, Gerrit, GitHub Enterprise and Pagure. These platforms operate drivers that help Zuul have a configured connection with external systems by implementing the functionality required to connect to them. These drivers can perform any of the following functions:\n\nSources – drivers host git repositories for projects. Zuul can clone these git repositories for projects and download refs.\nTriggers – drivers emit events; Zuul may respond to these triggers, which are configured in pipelines to cause changes or other refs to be enqueued.\nReporters – drivers output information when a pipeline is finished processing an item.\nSome of the drivers included with Zuul are: \n\nGitHub supports all three of the functions mentioned above, sources, triggers and reporters. It can also interact with public GitHub service and site-local installations of GitHub enterprise.\nGerrit acts as a code review system and its driver supports sources, triggers and reporters.\nPagure, like Github, Pagure drivers support all three of the functions mentioned earlier, sources, triggers and reporters. It can also interact with public Pagure.io service and site-local installations of Pagure.\nGit can be used to load Zuul’s configurations from public git repositories. It also performs the trigger function to trigger jobs from ref-updated events in a pipeline.\nZuul further includes other drivers such as MQTT, SMTP, SQL, Timer and Zuul itself. The first three of these drivers support reporters only whereas the latter two support only triggers.\n\nHaving multi-repository dependencies comes with benefits for all Zuul users,\n\nMultiple repositories make it easy to give access to subsets of repositories on a “need to code” basis.\nEach repository can have its own process of being deployed, making continuous delivery and deployment easier.\nDevelopers take advantage of multiple development platforms to create Adhoc continuous integration tests for exactly what they are working on at the moment.\nDevelopers also have the ability to work across project boundaries.\nCross community continuous integration testing is also supported via multi-repo.\nWith the option of GitHub Enterprise, all repository data can be stored on your organization’s local network and integrated with your organization’s authentication system.\n\nYou can read more about it here: https://vexxhost.com/blog/multi-repository-dependencies-zuul/ \nor check out: https://vexxhost.com/solutions/managed-zuul/",
"json_metadata": "{\"tags\":[\"devops\",\"continuousintegration\",\"technology\",\"github\",\"git\"],\"links\":[\"https://vexxhost.com/blog/multi-repository-dependencies-zuul/\",\"https://vexxhost.com/solutions/managed-zuul/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}mojo1jojo2followed @raise-me-up2019/10/08 19:46:15
mojo1jojo2followed @raise-me-up
2019/10/08 19:46:15
| required auths | [] |
| required posting auths | ["mojo1jojo2"] |
| id | follow |
| json | ["follow",{"follower":"mojo1jojo2","following":"raise-me-up","what":["blog"]}] |
| Transaction Info | Block #37112672/Trx 9a76eed82149f856e2da3d65cafc7984e0ab8e03 |
View Raw JSON Data
{
"trx_id": "9a76eed82149f856e2da3d65cafc7984e0ab8e03",
"block": 37112672,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-10-08T19:46:15",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"mojo1jojo2"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"mojo1jojo2\",\"following\":\"raise-me-up\",\"what\":[\"blog\"]}]"
}
]
}mojo1jojo2followed @sp-group2019/10/08 19:46:15
mojo1jojo2followed @sp-group
2019/10/08 19:46:15
| required auths | [] |
| required posting auths | ["mojo1jojo2"] |
| id | follow |
| json | ["follow",{"follower":"mojo1jojo2","following":"sp-group","what":["blog"]}] |
| Transaction Info | Block #37112672/Trx 7ca624fa87145b4d9ab371f5f11209c1bd4b5e2e |
View Raw JSON Data
{
"trx_id": "7ca624fa87145b4d9ab371f5f11209c1bd4b5e2e",
"block": 37112672,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-10-08T19:46:15",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"mojo1jojo2"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"mojo1jojo2\",\"following\":\"sp-group\",\"what\":[\"blog\"]}]"
}
]
}mojo1jojo2followed @marcusmalone2019/10/08 19:46:12
mojo1jojo2followed @marcusmalone
2019/10/08 19:46:12
| required auths | [] |
| required posting auths | ["mojo1jojo2"] |
| id | follow |
| json | ["follow",{"follower":"mojo1jojo2","following":"marcusmalone","what":["blog"]}] |
| Transaction Info | Block #37112671/Trx 571a4369ca8da5176aa778c8ec16b1c0d7ccbfc3 |
View Raw JSON Data
{
"trx_id": "571a4369ca8da5176aa778c8ec16b1c0d7ccbfc3",
"block": 37112671,
"trx_in_block": 25,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-10-08T19:46:12",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"mojo1jojo2"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"mojo1jojo2\",\"following\":\"marcusmalone\",\"what\":[\"blog\"]}]"
}
]
}mojo1jojo2published a new post: jenkins-vs-zuul-ci-cd-tool-comparison2019/10/07 15:07:21
mojo1jojo2published a new post: jenkins-vs-zuul-ci-cd-tool-comparison
2019/10/07 15:07:21
| parent author | |
| parent permlink | technology |
| author | mojo1jojo2 |
| permlink | jenkins-vs-zuul-ci-cd-tool-comparison |
| title | CI/CD Tools: Taking a Closer look at Zuul |
| body | As the development and testing of builds continues to grow not only in complexity but also in scale, the need for improved, efficient management of approvals and merges has evolved as well. This is where the concepts and practices of CI/CD tools have shown their value, and, as a result, have given way to the development of CI tools such as Zuul. Zuul was originally developed back in 2012 for CI testing, enabling users and contributors, spanning numerous diverse organizations, to efficiently and effectively develop together across multiple projects. Essentially, the problem that Zuul was designed to solve is that of providing developers with a tool to test serialized future states faster than was possible when executing the tests serially. The concept of pipeline being borrowed from processor design provided a sort of “optimistic speculation” by which one could effectively parallelize this testing in cases where jobs were likely to pass. It later became a tool for the automatic merging, building and testing of any new changes being made to a project, delivering an automated gated workflow pipeline. It is through this gating that new code is prevented from making it to production without passing project keeper defined unit and integration tests. You can read additional information on Zuul here: https://vexxhost.com/blog/getting-to-know-zuul-openstacks-ci-tool/ |
| json metadata | {"tags":["devops","tech"],"app":"steemit/0.1","format":"markdown","links":["https://vexxhost.com/blog/getting-to-know-zuul-openstacks-ci-tool/"]} |
| Transaction Info | Block #37078361/Trx 27c20931969a1ed81dc0881d349bfacaeb0a5295 |
View Raw JSON Data
{
"trx_id": "27c20931969a1ed81dc0881d349bfacaeb0a5295",
"block": 37078361,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-10-07T15:07:21",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "technology",
"author": "mojo1jojo2",
"permlink": "jenkins-vs-zuul-ci-cd-tool-comparison",
"title": "CI/CD Tools: Taking a Closer look at Zuul",
"body": "As the development and testing of builds continues to grow not only in complexity but also in scale, the need for improved, efficient management of approvals and merges has evolved as well. This is where the concepts and practices of CI/CD tools have shown their value, and, as a result, have given way to the development of CI tools such as Zuul. \n\nZuul was originally developed back in 2012 for CI testing, enabling users and contributors, spanning numerous diverse organizations, to efficiently and effectively develop together across multiple projects. Essentially, the problem that Zuul was designed to solve is that of providing developers with a tool to test serialized future states faster than was possible when executing the tests serially. The concept of pipeline being borrowed from processor design provided a sort of “optimistic speculation” by which one could effectively parallelize this testing in cases where jobs were likely to pass. It later became a tool for the automatic merging, building and testing of any new changes being made to a project, delivering an automated gated workflow pipeline. It is through this gating that new code is prevented from making it to production without passing project keeper defined unit and integration tests.\n\nYou can read additional information on Zuul here: https://vexxhost.com/blog/getting-to-know-zuul-openstacks-ci-tool/",
"json_metadata": "{\"tags\":[\"devops\",\"tech\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\",\"links\":[\"https://vexxhost.com/blog/getting-to-know-zuul-openstacks-ci-tool/\"]}"
}
]
}minibotupvoted (50.00%) @mojo1jojo2 / jenkins-vs-zuul-ci-cd-tool-comparison2019/10/02 20:49:57
minibotupvoted (50.00%) @mojo1jojo2 / jenkins-vs-zuul-ci-cd-tool-comparison
2019/10/02 20:49:57
| voter | minibot |
| author | mojo1jojo2 |
| permlink | jenkins-vs-zuul-ci-cd-tool-comparison |
| weight | 5000 (50.00%) |
| Transaction Info | Block #36941487/Trx d4e17a5202b9fab9aa0d7798d17f38de76633951 |
View Raw JSON Data
{
"trx_id": "d4e17a5202b9fab9aa0d7798d17f38de76633951",
"block": 36941487,
"trx_in_block": 11,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-10-02T20:49:57",
"op": [
"vote",
{
"voter": "minibot",
"author": "mojo1jojo2",
"permlink": "jenkins-vs-zuul-ci-cd-tool-comparison",
"weight": 5000
}
]
}anomalyupvoted (1.00%) @mojo1jojo2 / jenkins-vs-zuul-ci-cd-tool-comparison2019/10/02 20:49:06
anomalyupvoted (1.00%) @mojo1jojo2 / jenkins-vs-zuul-ci-cd-tool-comparison
2019/10/02 20:49:06
| voter | anomaly |
| author | mojo1jojo2 |
| permlink | jenkins-vs-zuul-ci-cd-tool-comparison |
| weight | 100 (1.00%) |
| Transaction Info | Block #36941470/Trx fd5ca35c0231decf701f447da0415aab8398396a |
View Raw JSON Data
{
"trx_id": "fd5ca35c0231decf701f447da0415aab8398396a",
"block": 36941470,
"trx_in_block": 19,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-10-02T20:49:06",
"op": [
"vote",
{
"voter": "anomaly",
"author": "mojo1jojo2",
"permlink": "jenkins-vs-zuul-ci-cd-tool-comparison",
"weight": 100
}
]
}mojo1jojo2published a new post: jenkins-vs-zuul-ci-cd-tool-comparison2019/10/02 20:48:09
mojo1jojo2published a new post: jenkins-vs-zuul-ci-cd-tool-comparison
2019/10/02 20:48:09
| parent author | |
| parent permlink | technology |
| author | mojo1jojo2 |
| permlink | jenkins-vs-zuul-ci-cd-tool-comparison |
| title | Jenkins vs Zuul: CI/CD Tool Comparison |
| body | Blog |
| json metadata | {"tags":["devops","tech"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #36941451/Trx a784eb7e02c98ca8419b29fcfbb0680bd8082111 |
View Raw JSON Data
{
"trx_id": "a784eb7e02c98ca8419b29fcfbb0680bd8082111",
"block": 36941451,
"trx_in_block": 12,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-10-02T20:48:09",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "technology",
"author": "mojo1jojo2",
"permlink": "jenkins-vs-zuul-ci-cd-tool-comparison",
"title": "Jenkins vs Zuul: CI/CD Tool Comparison",
"body": "Blog",
"json_metadata": "{\"tags\":[\"devops\",\"tech\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}nin4iupvoted (50.00%) @mojo1jojo2 / jenkins-vs-zuul-ci-cd-tool-comparison2019/10/02 20:19:57
nin4iupvoted (50.00%) @mojo1jojo2 / jenkins-vs-zuul-ci-cd-tool-comparison
2019/10/02 20:19:57
| voter | nin4i |
| author | mojo1jojo2 |
| permlink | jenkins-vs-zuul-ci-cd-tool-comparison |
| weight | 5000 (50.00%) |
| Transaction Info | Block #36940888/Trx 5ff64503e07fb9e6a3f1a882de369b47cf3ea523 |
View Raw JSON Data
{
"trx_id": "5ff64503e07fb9e6a3f1a882de369b47cf3ea523",
"block": 36940888,
"trx_in_block": 12,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-10-02T20:19:57",
"op": [
"vote",
{
"voter": "nin4i",
"author": "mojo1jojo2",
"permlink": "jenkins-vs-zuul-ci-cd-tool-comparison",
"weight": 5000
}
]
}mojo1jojo2published a new post: jenkins-vs-zuul-ci-cd-tool-comparison2019/10/02 16:55:09
mojo1jojo2published a new post: jenkins-vs-zuul-ci-cd-tool-comparison
2019/10/02 16:55:09
| parent author | |
| parent permlink | technology |
| author | mojo1jojo2 |
| permlink | jenkins-vs-zuul-ci-cd-tool-comparison |
| title | Jenkins vs Zuul: CI/CD Tool Comparison |
| body |  For the longest time, Jenkins has been the only tool when it comes to Continuous Integration (CI) and even to some extent, Continuous Delivery (CD). However, there has been a continuous rise in the need for a riskfree tool to integrate and deliver software stably and frequently. Such a requirement lead to the development of the open-source CI/CD tool Zuul, with a specialization in project gating. Although strides have been made to improve Jenkins, some of its problems are intractable. Here is a Zuul vs Jenkins account to better understand what is missing in one tool that the other makes up for. Looking at the problems that come with Jenkins, it seems like it is time to move over. With the development of promising CI/CD tools like Zuul, users’ options are no longer limited. Zuul has proven itself at scale in the OpenStack development process while also being suitable for small to mid-size businesses. As more users and use cases emerge, it is evident that Zuul is a game-changer for developers. It not only overcomes the shortcoming of Jenkins but also includes additional benefits. With project-gating being its forefront feature, you can rest easy knowing that no broken code is merged into the main branch. You can read the full account on the tools here: https://vexxhost.com/blog/jenkins-vs-zuul/ |
| json metadata | {"tags":["technology","devops","tech"],"image":["https://cdn.steemitimages.com/DQmQKCegyqsLdYcK11Gkk2VEFwc4riiAef1FAAE2JF5SxzU/Jenkins%20vs%20Zuul.jpg"],"links":["https://vexxhost.com/blog/jenkins-vs-zuul/"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #36936804/Trx 73a6e3f3eb31cbcccd7c5e8aa1415b64f99c82d5 |
View Raw JSON Data
{
"trx_id": "73a6e3f3eb31cbcccd7c5e8aa1415b64f99c82d5",
"block": 36936804,
"trx_in_block": 23,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-10-02T16:55:09",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "technology",
"author": "mojo1jojo2",
"permlink": "jenkins-vs-zuul-ci-cd-tool-comparison",
"title": "Jenkins vs Zuul: CI/CD Tool Comparison",
"body": "\n\nFor the longest time, Jenkins has been the only tool when it comes to Continuous Integration (CI) and even to some extent, Continuous Delivery (CD). However, there has been a continuous rise in the need for a riskfree tool to integrate and deliver software stably and frequently. Such a requirement lead to the development of the open-source CI/CD tool Zuul, with a specialization in project gating. Although strides have been made to improve Jenkins, some of its problems are intractable. Here is a Zuul vs Jenkins account to better understand what is missing in one tool that the other makes up for. \n\nLooking at the problems that come with Jenkins, it seems like it is time to move over. With the development of promising CI/CD tools like Zuul, users’ options are no longer limited. Zuul has proven itself at scale in the OpenStack development process while also being suitable for small to mid-size businesses. As more users and use cases emerge, it is evident that Zuul is a game-changer for developers. It not only overcomes the shortcoming of Jenkins but also includes additional benefits. With project-gating being its forefront feature, you can rest easy knowing that no broken code is merged into the main branch. \n\nYou can read the full account on the tools here: https://vexxhost.com/blog/jenkins-vs-zuul/",
"json_metadata": "{\"tags\":[\"technology\",\"devops\",\"tech\"],\"image\":[\"https://cdn.steemitimages.com/DQmQKCegyqsLdYcK11Gkk2VEFwc4riiAef1FAAE2JF5SxzU/Jenkins%20vs%20Zuul.jpg\"],\"links\":[\"https://vexxhost.com/blog/jenkins-vs-zuul/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}steemdelegated 18.223 SP to @mojo1jojo22019/09/30 17:07:42
steemdelegated 18.223 SP to @mojo1jojo2
2019/09/30 17:07:42
| delegator | steem |
| delegatee | mojo1jojo2 |
| vesting shares | 29673.472774 VESTS |
| Transaction Info | Block #36879572/Trx 92f3f716347ad27a85bc3e30adb9e6ed32e9682c |
View Raw JSON Data
{
"trx_id": "92f3f716347ad27a85bc3e30adb9e6ed32e9682c",
"block": 36879572,
"trx_in_block": 19,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-09-30T17:07:42",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "mojo1jojo2",
"vesting_shares": "29673.472774 VESTS"
}
]
}mojo1jojo2updated their account properties2019/09/30 15:21:24
mojo1jojo2updated their account properties
2019/09/30 15:21:24
| account | mojo1jojo2 |
| memo key | STM82gAZWJND6keUGKH9gMty4hk5d5p6YadYTyvBtv4RhU7LcekkQ |
| json metadata | {"profile":{"name":"talkabouttech"}} |
| Transaction Info | Block #36877448/Trx 006a21a0613bfa774db6c4159ac6ad9503af3348 |
View Raw JSON Data
{
"trx_id": "006a21a0613bfa774db6c4159ac6ad9503af3348",
"block": 36877448,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-09-30T15:21:24",
"op": [
"account_update",
{
"account": "mojo1jojo2",
"memo_key": "STM82gAZWJND6keUGKH9gMty4hk5d5p6YadYTyvBtv4RhU7LcekkQ",
"json_metadata": "{\"profile\":{\"name\":\"talkabouttech\"}}"
}
]
}steemdelegated 18.608 SP to @mojo1jojo22019/09/30 15:12:15
steemdelegated 18.608 SP to @mojo1jojo2
2019/09/30 15:12:15
| delegator | steem |
| delegatee | mojo1jojo2 |
| vesting shares | 30300.000000 VESTS |
| Transaction Info | Block #36877267/Trx e94ddad8a4ee447072053f2f409165eb59200d2d |
View Raw JSON Data
{
"trx_id": "e94ddad8a4ee447072053f2f409165eb59200d2d",
"block": 36877267,
"trx_in_block": 24,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-09-30T15:12:15",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "mojo1jojo2",
"vesting_shares": "30300.000000 VESTS"
}
]
}steemcreated a new account: @mojo1jojo22019/09/30 15:12:15
steemcreated a new account: @mojo1jojo2
2019/09/30 15:12:15
| creator | steem |
| new account name | mojo1jojo2 |
| owner | {"weight_threshold":1,"account_auths":[],"key_auths":[["STM66bYwKRrHsaBim2jp8yfvsvE62zcUcicNGxcPUz3qymZ2oS7Sw",1]]} |
| active | {"weight_threshold":1,"account_auths":[],"key_auths":[["STM8eReYD1Ai4QYNHqpSxoueAvFLGZ3b7fwTbed2ZmP2rPYXneNqt",1]]} |
| posting | {"weight_threshold":1,"account_auths":[],"key_auths":[["STM6k2ZHYuRMkdWT7uyMzgkwJAD82yUxw1tYju59WowpypgebhRJj",1]]} |
| memo key | STM82gAZWJND6keUGKH9gMty4hk5d5p6YadYTyvBtv4RhU7LcekkQ |
| json metadata | {} |
| extensions | [] |
| Transaction Info | Block #36877267/Trx e94ddad8a4ee447072053f2f409165eb59200d2d |
View Raw JSON Data
{
"trx_id": "e94ddad8a4ee447072053f2f409165eb59200d2d",
"block": 36877267,
"trx_in_block": 24,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-09-30T15:12:15",
"op": [
"create_claimed_account",
{
"creator": "steem",
"new_account_name": "mojo1jojo2",
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM66bYwKRrHsaBim2jp8yfvsvE62zcUcicNGxcPUz3qymZ2oS7Sw",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM8eReYD1Ai4QYNHqpSxoueAvFLGZ3b7fwTbed2ZmP2rPYXneNqt",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM6k2ZHYuRMkdWT7uyMzgkwJAD82yUxw1tYju59WowpypgebhRJj",
1
]
]
},
"memo_key": "STM82gAZWJND6keUGKH9gMty4hk5d5p6YadYTyvBtv4RhU7LcekkQ",
"json_metadata": "{}",
"extensions": []
}
]
}Manabar
Voting Power100.00%
Downvote Power100.00%
Resource Credits100.00%
Reputation Progress0.00%
{
"voting_manabar": {
"current_mana": 1953311140,
"last_update_time": 1588943256
},
"downvote_manabar": {
"current_mana": 488327785,
"last_update_time": 1588943256
},
"rc_account": {
"account": "mojo1jojo2",
"rc_manabar": {
"current_mana": "15767359412",
"last_update_time": 1588943256
},
"max_rc_creation_adjustment": {
"amount": "5934720390",
"precision": 6,
"nai": "@@000000037"
},
"max_rc": "7888031530"
}
}Account Metadata
| POSTING JSON METADATA | |
| None | |
| JSON METADATA | |
| profile | {"name":"talkabouttech"} |
{
"posting_json_metadata": {},
"json_metadata": {
"profile": {
"name": "talkabouttech"
}
}
}Auth Keys
Owner
Single Signature
Public Keys
STM66bYwKRrHsaBim2jp8yfvsvE62zcUcicNGxcPUz3qymZ2oS7Sw1/1
Active
Single Signature
Public Keys
STM8eReYD1Ai4QYNHqpSxoueAvFLGZ3b7fwTbed2ZmP2rPYXneNqt1/1
Posting
Single Signature
Public Keys
STM6k2ZHYuRMkdWT7uyMzgkwJAD82yUxw1tYju59WowpypgebhRJj1/1
Memo
STM82gAZWJND6keUGKH9gMty4hk5d5p6YadYTyvBtv4RhU7LcekkQ
{
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM66bYwKRrHsaBim2jp8yfvsvE62zcUcicNGxcPUz3qymZ2oS7Sw",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM8eReYD1Ai4QYNHqpSxoueAvFLGZ3b7fwTbed2ZmP2rPYXneNqt",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM6k2ZHYuRMkdWT7uyMzgkwJAD82yUxw1tYju59WowpypgebhRJj",
1
]
]
},
"memo": "STM82gAZWJND6keUGKH9gMty4hk5d5p6YadYTyvBtv4RhU7LcekkQ"
}Witness Votes
0 / 30
No active witness votes.
[]